Query full; need extra record source!

[New to Perl]

I'm practically still a newbie at access and I need some help !

Right now I created a tabbed form which initially is based on 1 query.
However, the query has reached its limit & i had to add another tab
with fields that need a record source.

So far about 10 tabs are based on this 1 query; and this new tab i
added has about 25 fields that need to be linked

I have tried linking the fields on this new tab directly to fields in
a table but i still get the Name error

is there a way for me to add 2 record sources? One would be the
initial query and the other a table for this new tab

any suggestions are welcomed?

 

[John W. Vinson]

I'm practically still a newbie at access and I need some help !

Right now I created a tabbed form which initially is based on 1 query.
However, the query has reached its limit & i had to add another tab
with fields that need a record source.

So far about 10 tabs are based on this 1 query; and this new tab i
added has about 25 fields that need to be linked

I have tried linking the fields on this new tab directly to fields in
a table but i still get the Name error

is there a way for me to add 2 record sources? One would be the
initial query and the other a table for this new tab

any suggestions are welcomed?

STOP!!!

If you have more than 20 or so fields in a table... *your table design is
almost certainly wrong*.

If you have over 255 fields (the limit) in a query, *your query design is
almost certainly wrong*.

"Fields are expensive, records are cheap". I strongly suspect you have
repeating fields - like Question1, Question2, Question63 - in your table...
right? If so, you need to redesign.

What ARE your tables? How are they related?

 

[Arvin Meyer [MVP]]

Probably, but without even looking at your database, I'd bet you have a
design problem that needs being fixed before you proceed.

First, I can't imagine a query reaching a limit. I've written queries that
returned hundreds of thousands of row while stress testing a database and
never found a limit.

Second, no form needs 10 tabs.

Third, it is rare that a table, especially a subtable needs as many as 25
fields.

At this point, adding anything to your query or form, would most likely
compound your problems further. I suggest that you re-read some database
design principles, either by Googling for them, or an excellent book written
by Michael J. Hernandez is available, named: "Database Design for Mere
Mortals"

 

[New to Perl]

Probably, but without even looking at your database, I'd bet you have a
design problem that needs being fixed before you proceed.

First, I can't imagine a query reaching a limit. I've written queries that
returned hundreds of thousands of row while stress testing a database and
never found a limit.

Second, no form needs 10 tabs.

Third, it is rare that a table, especially a subtable needs as many as 25
fields.

At this point, adding anything to your query or form, would most likely
compound your problems further. I suggest that you re-read some database
design principles, either by Googling for them, or an excellent book written
by Michael J. Hernandez is available, named: "Database Design for Mere
Mortals"
--
Arvin Meyer, MCP, MVPhttp://www.datastrat.comhttp://www.mvps.org/accesshttp://www.accessmvp.com










- Show quoted text -

I tried placing a button on an existing tab. This new button will link
to the new form i created with the 29 fields. The new form will then
have a new record source. My new issue is saving information entered
on this new form under the same autonumber as the existing tabbed
form.

Is there a way for me to link autonumbers so that for instance if I
enter information on the existing tabbed form where it will have a new
autonumber assigned; if I click the button to link to the extra form
that all information will be stored under 1 autonumber?

any suggestions?

 

[John W. Vinson]

I tried placing a button on an existing tab. This new button will link
to the new form i created with the 29 fields. The new form will then
have a new record source. My new issue is saving information entered
on this new form under the same autonumber as the existing tabbed
form.

You can't.

Is there a way for me to link autonumbers
No.

so that for instance if I
enter information on the existing tabbed form where it will have a new
autonumber assigned; if I click the button to link to the extra form
that all information will be stored under 1 autonumber?

An autonumber has ONE PURPOSE ONLY: to provide a unique, unrelated to anything
else, not dependent on anything else, meaningless identifier. If you want to
control the value of a field, you *cannot* use an autonumber for that field.

I still strongly suspect that your table design is at the root of your
troubles, but if you really do need a one to one relationship between two
tables, using the same value as the primary key, then the second table's
primary key must be a Long Integer number, *NOT* an Autonumber. You can have
it fill in automatically by using a Subform, using the autonumber field as the
Master Link Field and the related long integer field as the Child Link Field;
or - if you insist on making your job and your users' jobs harder - put VBA
code in the form-open command and the form's Open event to pass the autonumber
value via the form's OpenArgs property, and set the default value of the child
table's primary key in the popup form's open event.

So... STOP. Your first step should be to review the normalization of your
table structure. If you keep fighting with forms, adding new controls, adding
new tabs, adding new forms to overcome a flawed table design, you're on the
wrong track! "If you find yourself in a deep hole, the first thing is to stop
digging".

We're not attacking you here, Janet. We're trying to help. We've all been
where you are now, and have gotten help from others - and found that properly
normalizing data really DOES make a big improvement, as soon as the (rather
steep and rocky) learning curve is climbed.