Frank said:
I have converted my mdb over to adp and the main
form looks good but the subforms do not allow data
entry.
Just as a matter of interest, why would you do that? Particularly since the
Access team in Redmond has overcome the marketing hype and false enthusiasm
for ADP in the last few years and now recommends MDB or ACCDB with ODBC
connection to SQL Server as the configuration of choice. If you'd been
keeping up with this newsgroup, you'd have seen that there are quite a few
recommendations to switch to ADP and SQL Server, but the vast majority of
them are from one poster -- long on vulgarity, long on insult, but short on
technical detail; knowledgeable developers have been reminding people of the
Access team's current recommendation for at least the last three years.
I am using SQL Server 2000, and the database looks
fine. Is there a settings I should check for the subforms?
In my one "significant" experience with ADP/ADO, all the forms were unbound,
not as a matter of design or performance, but because the original author
had simply not realized that to use bound forms with ADP, the SQL Server
tables must (repeat MUST) have a primary key specified. I was only
enhancing, not re-working, the app, so only encountered one form/subform;
when I got the DBA to specify a primary key on the tables involved, it
worked just fine.
Do all the tables either directly involved, or referenced in queries used,
have a primary key? Are your queries updateable? Whether ADP or MDB, that's
the most common cause of "won't update" problems.
Larry Linson
Microsoft Office Access MVP
