'invalid control property' and 'too many fields defined'

T

TBA

Almost had finished building a set simple data entry forms when everything
turned to custard! help!
brief structure description-
10 tables linked by a single key (Primary in one table only)
a series of tabbed forms linking to table fields.

what happened:
on last form page tried to place a table field in and Access said:
"No fields available to be added to the current view
The current recordsource might be invalid...(etc)"

I then saved and closed.
when opeining again the mainform won't enter form mode with the following
error:
"too many fields defined"

I compacted and repaired the dtabase, but same problem.

I now note all fields have the green error flag and two lines are indicated:
"Invalid control property:control source
No such field in the filed list"

any help on pointing me in the right direction very gratefully accepted!!
Theo
 
D

Dale Fye

My first guess would be that you have more than 255 fields in the forms
RecordSource. check out the following URL for some of the Access
specifications.

(http://www.databasedev.co.uk/access_specifications.html)

If this is the case, I strongly recommend that you create subforms for the
various tabs. But all of the controls that belong on each tab in a subform,
then put the subform on each tab.

When I do this, I generally set the SourceObject of each of the subforms to
"", then, in the tab controls Change event, I check to see whether the
SourceObject is blank, and if it is, I set it to the appropriate subform name.

This speeds up the initial load of the main form.


--
HTH
Dale

email address is invalid
Please reply to newsgroup only.
 
T

TBA

thanks Dale- I'll give it a try. I counted the fields and they were more than
255. so I split one form out. the subform idea is much better and means I can
maintain a single tabbed form for all the work.

cheers Theo
 
T

TBA

Hi again Dale
just needed a little further clarification if you get this-
what seems to work is creating new forms from each tab, and then using these
as the source of each subform back on the mainform.
I see where to enter the Source object on each subform- but you are saying
to make this a blank field?
I am not so sure on finding the "tab controls Change event, I check to see
whether the SourceObject is blank, and if it is, I set it to the appropriate
subform name."
if I have located the right place it is on the 'Event' tab of the property
sheet and the field is 'On Change'. It has [Event Procedure] in it now? what
am I entering in there?
many thanks Theo
 
D

Dale Fye

Try it with just setting the Source Object to the appropriate form, and
setting the master and child fields. If that works fine, and there is not
too much delay when the form is loaded, just stick with it.

In one of my applications, several of the subform record sources were based
on complex queries, and took too long to run. Since I didn't go to those
subforms on a frequent basis, I just started leaving the SourceObject blank
on those subforms until I got to the tab they were on. At that time, I
would check to see if the subform was loaded, and if not, would set the
source object property

HTH
Dale

TBA said:
Hi again Dale
just needed a little further clarification if you get this-
what seems to work is creating new forms from each tab, and then using
these
as the source of each subform back on the mainform.
I see where to enter the Source object on each subform- but you are
saying
to make this a blank field?
I am not so sure on finding the "tab controls Change event, I check to see
whether the SourceObject is blank, and if it is, I set it to the
appropriate
subform name."
if I have located the right place it is on the 'Event' tab of the property
sheet and the field is 'On Change'. It has [Event Procedure] in it now?
what
am I entering in there?
many thanks Theo

Dale Fye said:
My first guess would be that you have more than 255 fields in the forms
RecordSource. check out the following URL for some of the Access
specifications.

(http://www.databasedev.co.uk/access_specifications.html)

If this is the case, I strongly recommend that you create subforms for
the
various tabs. But all of the controls that belong on each tab in a
subform,
then put the subform on each tab.

When I do this, I generally set the SourceObject of each of the subforms
to
"", then, in the tab controls Change event, I check to see whether the
SourceObject is blank, and if it is, I set it to the appropriate subform
name.

This speeds up the initial load of the main form.


--
HTH
Dale

email address is invalid
Please reply to newsgroup only.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top