Items in form cannot be seen in Form View?

[fredalina]

i have a form that is giving me trouble, and has been for ages. Everything looks good in design view, and the Properties for all fields and items are set to Visible? Yes and Display When? Always. However, when I open the form in form view, it appears to be blank. Only the background can be seen. The navigation area at the bottom is grayed out and shows no records.

i had somehow gotten this to work properly (and promptly forgot what I did, so that a year plus later I don't remember how i fixed it previous), but spontaneously last week it stopped working again. Some changes were made to the server that houses the backend, but I can't think that this could be related.

Have you seen this? Can this form be salvaged?

 

[pbaldy]

It sounds like a combination of no records to display and the form (or underlying source) doesn't allow additions. In that instance, the form can open with all the controls hidden.

 

[fredalina]

There is data in the table and it is set to allow additions.

I have even found an older version of the database where the form opens correctly and everything is viewable, and imported it into the current database, and it is invisible after the import. Is it possible there is some database setting that would impact this? (It is only this one form, though). Right now I am trying to copy the older form and paste it into the current db. Beyond that All i can think of is to copy all of the fields and procedures.

Any other suggestions? Thanks!

 

[missinglinq]

Paul's suggestion is the usual explanation of this phenomenon, in fact is the only explanation of this type of behavior! But there are some other things to take into account.

Having AllowAdditions set to Yes/True doesn't insure that the form can have records added! If the form is based on a query there are a number of things that can make it Read-Only.

You say that there are records present, but can your form access them? Maybe some of the changes made to the server is preventing access. Once again, if the form is based on a multi-table query, its structure can prevent any records from being shown.

Obviously, something has changed between the previous version of your database and the current one, and from what you've said, I'd place money on the server changes.

 

[fredalina]

The form refers directly to one single table (no query), and it is set to allow additions and edits. There are records in the table. Thanks!

 

[fredalina]

Also, if this were the problem, why would none of the controls be visible in the form at all? I can understand why fields would be blank/grayed out/etc, but there is nothing visible whatsoever except the background. It's very confusing. Even after I import a form from an older version that works perfectly, it encounters the same problem. And the older versions refer to the same backend on the same server, so if the server were the problem, should it not affect the older versions as well?

 

[missinglinq]

Also, if this were the problem, why would none of the controls be visible in the form at all?

Because when conditions are as Paul and I have described, that's how Access behaves!

Even after I import a form from an older version that works perfectly, it encounters the same problem. And the older versions refer to the same backend on the same server, so if the server were the problem, should it not affect the older versions as well?

So if you run the old version form in the old version database, it runs correctly?
And you run the old version form in the new version database and it bombs?

If this is correct then it would appear that while your old version database is connected correctly to the back end, your new version database is not. Do other forms in the newer database connect to the back end without problem?

The only other thing I can think of is corruption, but in 10 years of contributing both here and to five or six other forums on a daily basis, I have never seen a report of corruption presenting in this way.

 

[gemma-the-husky]

fred

you ought to test this carefully

in the form open event add

msgbox(dcount("*",me.recordsource))

this will confirm exactly how many records ought to be available

--------------

the circumstances you describe reflect a form with no records to display, and where additions are not possible. - as described already.

 

[dillon_gator]

Sorry, folks, but none of this helps. Any new ideas? I only have one record in my form because I want to make sure my form works before I dump in 3000. I'm am totally not understanding something here.

 

[DCrake]

Go to the design of the form
View the porperties of the form
In the first property Record Source click on the elipses button [...]
It will as you if you want to build a query based on the table... say yes
You will be taken into the query by design window.
Drag the * down to include all records
Click on view - datasheet mode
Do any records appear in the datasheet?

 

[missinglinq]

...Some changes were made to the server that houses the backend...

Sorry, I missed this the first time through. The fact that you actually have a record in the Record Source, and this is still happening, suggests that this is, indeed, the root of your problem! You have to have lost your Read/Write Permissions for the server that holds the back end when the server changes were made.

I believe that David's suggestion will bear this out.

Linq ;0)>