F
Fubu
I do all my database developing/coding on XP (Access
format 2000) and the database is then used in Access 2K.
The problem I am running into is that when I move the
database over to 2K I then how ever move it back to my
Laptop where I do all of the stuff they I do in it and
then I run it and the code looks fine but does not work
the way it should. I then copy it to a machine running
Access 2K and look at the code and the code gets all
messed up. Like I have 2 procedures. With Access 2K it
some how mixes the 2 together, but on Office XP it looks
just fine. Anyone know what is making it do this
corruption, or know a way for it not to happen? This is
the third time it has happened to me with 3 different
databases. I did not do any file conversion or code
conversion in the 3 databases. I have also made 5 other
databases in the same way and have had no problems, made
in the similar fashion.
format 2000) and the database is then used in Access 2K.
The problem I am running into is that when I move the
database over to 2K I then how ever move it back to my
Laptop where I do all of the stuff they I do in it and
then I run it and the code looks fine but does not work
the way it should. I then copy it to a machine running
Access 2K and look at the code and the code gets all
messed up. Like I have 2 procedures. With Access 2K it
some how mixes the 2 together, but on Office XP it looks
just fine. Anyone know what is making it do this
corruption, or know a way for it not to happen? This is
the third time it has happened to me with 3 different
databases. I did not do any file conversion or code
conversion in the 3 databases. I have also made 5 other
databases in the same way and have had no problems, made
in the similar fashion.