Suggestions
1. Split the database
Whenever you have have multiple users accessing the database, you need to
give each one a separate front end, with linked tables to the shared data.
If that is a new concept, see:
Split your MDB file into data and application
at:
http://allenbrowne.com/ser-01.html
2. Decompile
Each version of Access uses a different binary for the compiled code. You
can avoid some of these problems by decompiling before you give the front
end to users with a previous version.
Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then open it in Access 2000, open a code window, and choose Compile from the
Debug menu.
3. Service packs
This particular error can occur because the A2000 users are not up to date
with their Office or JET service packs:
http://support.microsoft.com/gp/sp http://support.microsoft.com/kb/239114
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"larpup" <la****@gmail.comwrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
I've written an app in A2003 only to find out that some customers are
presently using A2000.
Rather than place a runtime on their computer, it would be more
convenient to convert appt to A2000 if possible. I know how to convert
the file format, but when running an A2000 instance, if receive
"recordset not updateable". Is this possible?