Can someone respond please!!

  • Thread starter Thread starter Tamer Seoud
  • Start date Start date
T

Tamer Seoud

Hi everybody,
I posted the following problem a week ago on more than one
discussion group and nobody got back to me. Please,
anybody has an idea on how to solve it, let me know. I
don't believe there is no solution for it, but
unfortunately, I can't find any articles that discuss it.
Please someone respond back to me, I'm really stuck.

After I converted a DataBase from Access97 to Access2K,
everything worked well so far (ODBC Linked tables,
queries, reports) except for some forms that give me an
error message "ODBC cannot lock all records" whenever I
attempt to open these forms. In addition none of the
command buttons in these forms work. The forms work fine
in Access97.

Best Regards,
Tamer
 
It seems to me that you are having an incompatible version problem. There
were significant changes from AC97 to AC2000. One is the introduction of
ADO and that DAO is no longer a default reference. First place to look is
in the references for the database. Next make sure your declarations of
record sets and databases is correct. In fact check all your declare
statements that they are compatible with AC2000. Unfortunately, from an
AC97 programmer point of view AC2000 has many quirks. These quirks are just
the changes MS made to upgrade VB and VBA from Version 5 (AC97) to VB/VBA
version 6 (AC2000). I suggest you acquire the books "Access Developers
Handbook", Volume 1 and 2, authored by Getz and company, published by SYBEX.
Cheers,
Henry
 
Tamer Seoud said:
Hi everybody,
I posted the following problem a week ago on more than one
discussion group and nobody got back to me. Please,
anybody has an idea on how to solve it, let me know. I
don't believe there is no solution for it, but
unfortunately, I can't find any articles that discuss it.
Please someone respond back to me, I'm really stuck.

After I converted a DataBase from Access97 to Access2K,
everything worked well so far (ODBC Linked tables,
queries, reports) except for some forms that give me an
error message "ODBC cannot lock all records" whenever I
attempt to open these forms. In addition none of the
command buttons in these forms work. The forms work fine
in Access97.
Click to expand...

I don't know about this particular error, Tamer, so I can only suggest
some things to look into. My guess is that it's a change in the Jet
version, rather than the Access version itself, but I really don't know.

First question: What's the record locking strategy set for the forms in
question? Are the forms' Record Locks properties set to "All Records",
or anything different from those of the forms that don't have this
problem? If so, does the problem go away if you change that?

Second question: Is there anything unusual about the forms'
recordsources? Are these forms based on pass-through queries? Are
multiple tables involved? Do all of the tables involved have their
primary keys included in the recordsource?

Third question (for my information): What type of data source are you
linking to?
 
Tamer Seoud said:
Hi everybody,
I posted the following problem a week ago on more than one
discussion group and nobody got back to me. Please,
anybody has an idea on how to solve it, let me know. I
don't believe there is no solution for it, but
unfortunately, I can't find any articles that discuss it.
Please someone respond back to me, I'm really stuck.

After I converted a DataBase from Access97 to Access2K,
everything worked well so far (ODBC Linked tables,
queries, reports) except for some forms that give me an
error message "ODBC cannot lock all records" whenever I
attempt to open these forms. In addition none of the
command buttons in these forms work. The forms work fine
in Access97.
Click to expand...

A further suggestion: click Tools -> Options..., go to the Advanced
tab, and if Default Record Locking is set to "All records", change it to
"No locks" or "Edited record".
 
Have you tried refreshing your table links via the Linked
Table Manager.

Often when getting strange error messages or DAO error
messages, this simple process will solve the problem.

Good Luck
 
Check the References under tools, and locate what is missing. Most likely
VB3.6 engine is missing. Remember access 2000 uses a different VB. Anyhow
you should start there, and then open the code ,and compile it. You might
have to change some of the code manually
..
Let me know how this works
 
Back
Top