Access Form Problems w/SQL Backend

[Guest]

I have a SQL Server backend and an Access front end. The front end was built
in Access entirely, no SQL, and upgraded over the past month to the new
backend.

I have forms, lots of them. Many of the forms have a problem. Nearly all
of the forms are tied directly to the table, then opened using a macro and
query to narrow the data that is displayed.

In only about half of these forms, I have a problem where when I open the
form in design mode or get a null (no record found) result attempting to open
the form, in the form properties, second tab (Data), the second and third
lines (Filter and Order By) automatically fill in with some gibberish that
looks like the code version of the filter created by the query. I can delete
this gibberish, save, and the form will work until the next time I get a null
result or open the form in design again.

I have tried tying the form directly to the query and changing to a coded
opening of the form, but the same thing happens. I am not much of a coder
and have far too many forms to go back and change every single one of them,
anyway.

Any ideas how to stop this from happening?

 

[Albert D. Kallal]

For all of the sql tables, you need:

a primary key
a timestamp field

You MUST ensure both of the above fields are exposed to the form. Often,
when one builds forms with the wizard, you get a form based on a query, not
the table..and the PK and timestamp fields are not exposed to the form.

So, check your sql tables.....

As a general rule, you need both PK and timestamp fields exposed for the
forms to work smoothly.

 

[Albert D. Kallal]

I would also consider running your application as a mde....

 

[Guest]

I have the PKs, I will check that they are always showing on the form. I did
not create the tables into SQL with the timestamps. How can I add them after
the fact in a production database without affecting the database, or can I?

Do the PKs need to be included in the search criteria or just on the form
and in the query?