Upgrading from office 2000 to 2003

I have an access program that was written with 2000. One of the computers
that uses it was upgraded to 2003. When ever we tray to add a record to the
DB we get invalid use of null. Is there something i can do to fix the problem
on this machine

Gary, which of these 3 describe your situation:

a) All completely different copies of the database (i.e. each user is
working with different data).

b) All computers are opening the same MDB file (over a network).

c) Everyone is using the same data, but has a separate copy of the front end
(split database.)

If (a), decompiling will probably fix it.

If (b), switch to (c), and decompile the front end on the A2003 machine.

Suggested sequence for the decompile:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile 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"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

--
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.

"Gary W" wrote in message
...
I have an access program that was written with 2000. One of the computers
that uses it was upgraded to 2003. When ever we tray to add a record to
the
DB we get invalid use of null. Is there something i can do to fix the
problem
on this machine

Allen
First let me thank you for your help.
Second I have a little more info about the problem.
Let me clairify a couple of things! This program was written by someone else
several years ago. I am a VB programmer with not much experience is access.
The company that uses this has it networked. The data is stored on an XP
machine and shared. There is only 1 mdb and 1 mde. There are 3 XP machines
and 1 vista. I have a copy of this program at my location and it runs fine on
my 2000 (Office 2000) machine. I copied it to a machine that has XP with
Office 2003 and it ran fine. The location using the program (on the macine
that stores the program - XP with Office 2003) any time they add a record
using the data control they get invalid use of null. It happens on all the
macines that are networked also.I have not done the things you suggested yet
until I was able to clairify this info with you. Should I use Option b if so
should I do it on the XP or the Vista machine, or could there be some other
problem(weird windows security issue or something like that).

"Allen Browne" wrote:

Gary, which of these 3 describe your situation:

a) All completely different copies of the database (i.e. each user is
working with different data).

b) All computers are opening the same MDB file (over a network).

c) Everyone is using the same data, but has a separate copy of the front end
(split database.)

If (a), decompiling will probably fix it.

If (b), switch to (c), and decompile the front end on the A2003 machine.

Suggested sequence for the decompile:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile 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"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

--
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.

"Gary W" wrote in message
...
I have an access program that was written with 2000. One of the computers
that uses it was upgraded to 2003. When ever we tray to add a record to
the
DB we get invalid use of null. Is there something i can do to fix the
problem
on this machine

Okay, Gary, I strongly recommend you move to (c).

If the database is secured, place the MDW in the same folder as the back end
(i.e. the MDB), assuming it has a different name (otherwise that creates
problems with locking.)

I cannot promise this will fix this particular problem, but at very least it
will allow you to debug it without other machines interfering.

--
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.

"Gary W" wrote in message
...
Allen
First let me thank you for your help.
Second I have a little more info about the problem.
Let me clairify a couple of things! This program was written by someone
else
several years ago. I am a VB programmer with not much experience is
access.
The company that uses this has it networked. The data is stored on an XP
machine and shared. There is only 1 mdb and 1 mde. There are 3 XP machines
and 1 vista. I have a copy of this program at my location and it runs fine
on
my 2000 (Office 2000) machine. I copied it to a machine that has XP with
Office 2003 and it ran fine. The location using the program (on the macine
that stores the program - XP with Office 2003) any time they add a record
using the data control they get invalid use of null. It happens on all the
macines that are networked also.I have not done the things you suggested
yet
until I was able to clairify this info with you. Should I use Option b if
so
should I do it on the XP or the Vista machine, or could there be some
other
problem(weird windows security issue or something like that).

"Allen Browne" wrote:

Gary, which of these 3 describe your situation:

a) All completely different copies of the database (i.e. each user is
working with different data).

b) All computers are opening the same MDB file (over a network).

c) Everyone is using the same data, but has a separate copy of the front
end
(split database.)

If (a), decompiling will probably fix it.

If (b), switch to (c), and decompile the front end on the A2003 machine.

Suggested sequence for the decompile:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile 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"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

"Gary W" wrote in message
...
I have an access program that was written with 2000. One of the
computers that uses it was upgraded to 2003. When ever we tray to
add a record to the DB we get invalid use of null. Is there something
i can do to fix the problem on this machine