invisible form objects

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I posted this question on the general forum but seem to have stumped the folks there so I'll try it here

I have a form whose fields and controls are all suddenly invisible in form view. Everything shows up properly in design view but the form is empty in form view. Additionally, the record navigation at the bottom of the form is greyed out. If I import this form from a backup copy of my db where it's still working properly, the problem recurs after import. Please help

thanks
spence
 
spence said:
I posted this question on the general forum but seem to have stumped the
folks there so I'll try it here:
I have a form whose fields and controls are all suddenly invisible in
form view. Everything shows up properly in design view but the form is
empty in form view. Additionally, the record navigation at the bottom of
the form is greyed out. If I import this form from a backup copy of my db
where it's still working properly, the problem recurs after import. Please
help.

The detail section of a form will appear completely blank when there are no
current records to display and either the form or the recordset do not
allow new entries.

Do you have existing records?

Do you have a filter applied that might be limiting the records returned to
none?

Does the form have AllowAdditions set to yes?

Can you edit data directly in the table/query?
 
an update that may (or may not) shed some light on this peculiarity

while using backup files to try various fixes, i discovered that my form objects disappear after i run the compact and repair utility. once its been run on my database there seems to be no recovering the form because even if i import a working copy from a duplicate db w/o the issue, the imported form still has all its objects invisible

----- spence wrote: ----

I posted this question on the general forum but seem to have stumped the folks there so I'll try it here

I have a form whose fields and controls are all suddenly invisible in form view. Everything shows up properly in design view but the form is empty in form view. Additionally, the record navigation at the bottom of the form is greyed out. If I import this form from a backup copy of my db where it's still working properly, the problem recurs after import. Please help

thanks
spence
 
Rick

Thanks for the tips, but no such luck. To answer your questions
1. I do not have any records.
2. I am able to add records to the underlying tables
3. Allow additions is set to Yes on the for
4. No filters are applied

If I add a single record to the underlying table, the controls and fields in my form do indeed show up; however, when i do this, the "new record" button in the navigation becomes grayed out. I have a "go to new record" button on the form and it returns an error "cannot go to specified record.

sigh

thanks
spence
 
spence said:
Rick,

Thanks for the tips, but no such luck. To answer your questions:
1. I do not have any records.
2. I am able to add records to the underlying tables.

This is not what I asked. If your form is bound to a query or SQL
statement that contains more than one table it is very likely not
updateable. The fact that the individual tables are updateable doesn't
enter into it. My guess is that if you open the *query* being used by your
form you will find that edits and additions are not allowed and that is why
your form is behaving the way it is.

Very simple multi-table queries can often maintain the ability to edit
records, but the more tables you add the more likely that you will get a
read-only result set. This sort of query is more suitable for reports and
such, but not for editing data. For that you typically use forms and
subforms with each one bound to a single table.
 
I asked if he had any records in the microsoft.public.access group.

spence said:
Rick,

Thanks for the tips, but no such luck. To answer your questions:
1. I do not have any records.
2. I am able to add records to the underlying tables.

This is not what I asked. If your form is bound to a query or SQL
statement that contains more than one table it is very likely not
updateable. The fact that the individual tables are updateable doesn't
enter into it. My guess is that if you open the *query* being used by your
form you will find that edits and additions are not allowed and that is why
your form is behaving the way it is.

Very simple multi-table queries can often maintain the ability to edit
records, but the more tables you add the more likely that you will get a
read-only result set. This sort of query is more suitable for reports and
such, but not for editing data. For that you typically use forms and
subforms with each one bound to a single table.
 
Back
Top