Access 2002 to Access 2000

[DS]

I built a Database in Access XP 2002, File Format 2000.
I installed it on a machne running Access 2000 and I keep getting
Access generating Errors, creating a Log....First is this whole thing
incompatable, and Second where is this error log, can I fix this problem?
Thanks
DS

 

[Guest]

Hi DS,

First is this whole thing incompatable...

You should not be experiencing any compatibility problems. You should make
sure that all machines have the latest service packs installed for the
operating system, Office, and the JET database engine:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528

...and Second where is this error log, can I fix this problem?

I'm going to guess that it is a Dr. Watson error log. Search your hard drive
for a folder named DrWatson. The error might be logged to a file within this
folder named drwtsn32.log. However, I'm not sure how useful this information
will be to mere mortals.

Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Then import all objects from the suspect database into the new
database, one group at a time, into your new database. In other words, import
all tables (but not linked tables), then import all queries, then all forms,
etc. While Access will allow you to import all objects in one operation, the
experts at FMS, Inc. (a Microsoft Partner), have stated that it is best to
import objects one group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I built a Database in Access XP 2002, File Format 2000.
I installed it on a machine running Access 2000 and I keep getting
Access generating Errors, creating a Log....First is this whole thing
incompatable, and Second where is this error log, can I fix this problem?
Thanks
DS

 

[DS]

Hi DS,



You should not be experiencing any compatibility problems. You should make
sure that all machines have the latest service packs installed for the
operating system, Office, and the JET database engine:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528




I'm going to guess that it is a Dr. Watson error log. Search your hard drive
for a folder named DrWatson. The error might be logged to a file within this
folder named drwtsn32.log. However, I'm not sure how useful this information
will be to mere mortals.

Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Then import all objects from the suspect database into the new
database, one group at a time, into your new database. In other words, import
all tables (but not linked tables), then import all queries, then all forms,
etc. While Access will allow you to import all objects in one operation, the
experts at FMS, Inc. (a Microsoft Partner), have stated that it is best to
import objects one group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I built a Database in Access XP 2002, File Format 2000.
I installed it on a machine running Access 2000 and I keep getting
Access generating Errors, creating a Log....First is this whole thing
incompatable, and Second where is this error log, can I fix this problem?
Thanks
DS

Thanks Tom, I'll try it now. I was also wonder
ing can I install OfficeXP 2002 on Windows 2000?
Thanks
DS

 

[DS]

Hi DS,



You should not be experiencing any compatibility problems. You should make
sure that all machines have the latest service packs installed for the
operating system, Office, and the JET database engine:

How to keep a Jet 4.0 database in top working condition
http://support.microsoft.com/?id=303528




I'm going to guess that it is a Dr. Watson error log. Search your hard drive
for a folder named DrWatson. The error might be logged to a file within this
folder named drwtsn32.log. However, I'm not sure how useful this information
will be to mere mortals.

Create a brand new database and immediately disable the NameAutocorrupt
feature (see: http://allenbrowne.com/bug-03.html for reasons why you want to
do this). Then import all objects from the suspect database into the new
database, one group at a time, into your new database. In other words, import
all tables (but not linked tables), then import all queries, then all forms,
etc. While Access will allow you to import all objects in one operation, the
experts at FMS, Inc. (a Microsoft Partner), have stated that it is best to
import objects one group at a time (Reference:
http://www.fmsinc.com/ubb/Forum12/HTML/000285.html).

Recreate any linked tables from scratch. Access can cache a lot of
information about linked tables, which may no longer be valid, so it's always
best to recreate the linked tables from scratch. When importing local tables,
make sure to check the option to import relationships, menus and toolbars,
and import/export specs. If any of the local tables in the source DB are
hidden, you'll need to first unhide them. You will need to set the checked
references to match the source database, along with any startup options set
under Tools > Startup. Going through this process often times solves
corruption problems, because you get a new set of the hidden system tables
(the tables whose names start with "MSYS"). These system tables are updated
appropriately as you import objects.

This may sound like a lot of work, but it really isn't. Creating a new
container DB, disabling NameAutocorrect, importing all objects one group at a
time, re-establishing any linked tables, setting startup options, and setting
references to match the source DB is usually a fairly quick procedure. When
you are in the Visual Basic Editor, in order to check that the references
match the source DB, you should do a Debug > Compile ProjectName as well.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I built a Database in Access XP 2002, File Format 2000.
I installed it on a machine running Access 2000 and I keep getting
Access generating Errors, creating a Log....First is this whole thing
incompatable, and Second where is this error log, can I fix this problem?
Thanks
DS

Hey, Hey , Hey.......!
It worked! That made me happy! Thanks
I appreciate the time you took to explain it.
Once again Thank You
DS

 

[John Vinson]

can I install OfficeXP 2002 on Windows 2000?

Yep, works fine.

John W. Vinson[MVP]

 

[Guest]

Hi DS,

You're very welcome. I forgot to mention that this process of creating a
new database, and importing all objects, is one that a lot of developers,
including myself, do as preventative medicine just prior to converting to
..MDE and distributing to users. It's a fairly quick process, and you get a
brand new set of system tables, so it's worth doing on a regular basis.

Thanks for reporting your results back.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

Hey, Hey , Hey.......!
It worked! That made me happy! Thanks
I appreciate the time you took to explain it.
Once again Thank You
DS

 

[DS]

Yep, works fine.

John W. Vinson[MVP]

Thanks John
DS