Acess 2003 concurrent with acess 2007

[Scott]

We have a database written in Access 2003. The database is split with the
backend shared data on a fileserver. Each user machine has the front end with
forms code reports and the like. As we replace new computers we are using
Access 2007. So we have a mix of 2003 and 2007 Access. I have a couple of
questions.

Is there a problem running the same front end (written in 2003) on the 2007
and 2003 machines concurrently? Using the same backend.

I have noticed one problem. On some of the data entry forms on the 2007
machines I cant delete records. When I right click on the record to delete
the delete option is grayed out. I can open the data table and delete the
records. The delete record still works fine on the 2003 machines.

Thanks
Scott

 

[DeltaTech]

Hi

Microsoft Access is FORWARD compatable but not BACKWARD compatable.

You can import 2003 to 2007 but you can not import 2007 to 2003.

The problem woth the delete being faded out is that you OPENED the 2003 with
2007 in which case the result would be READ ONLY

You must import the 2003 into 2007
Be sure to make a copy to import DO NOT used the origional.
Once you import you 2003 into 2007 you can not correctly read the imported
2003 using Access 2003.

Regards
DeltaTech

 

[Paul Shapiro]

I have clients using a mix of Access 2003 and 2007 without problems. The
backend db has to stay in an Access-2003 compatible format. Each user MUST
have a local copy of the front end on their workstation. No one should ever
be running a shared copy of the front end. The front end has to be
distributed in Access 2003 format and has to be prepared with Access 2003.
Access 2007 will automatically update VBA references from 2003, but 2003
will not be able to update references from 2007. If the master copy of the
FE has ever been opened by A2007, then open it in A2003, adjust the
references and verify it compiles. If the clients have different operating
systems, it's best to prepare the master FE on the oldest os version using
the oldest Access version.

I didn't see any issues like you're describing with deleting from a form in
Access 2007. Did you verify the FE is compiled successfully in A2007? It's
also worth ensuring both the Access 2003 and 2007 workstations are current
with service packs and suggested hotfixes. A2007SP1 and A2003SP3 both need
some hotfixes to correct bugs introduced in the service packs.

For my own testing in this scenario, I found it easiest to use Virtual PC
and set up a virtual machine running the oldest operating system in use at
any of my clients and the oldest Access version. In my case it was Windows
XP/Access 2003. That let me test any reported issues and gave me the right
platform for building the master FE version.

If you're using any 3rd-party VBA references, those need to be identical on
all clients too.

 

[Scott]

Thanks for the help

About the delete record thing....I was accustom to using "ctrl -" in 2003 to
delete mulitiple records I dont think this works in 2007 on my forms but
works on my tables. Old habits I guess. Delete works fine if I highlight
records and press the delete key. I guess I wont be applying for a rocket
science job anytime soon.

About the compatibility thing I think I get it.

1. No editing the front end in 2007. AKA keep in 2003 format for distribution
2. Keep the back end in 2003 format

So when we eventually get all the clients on 2007 I can convert the FE and
BE to 2007.

So far everything is working using 2003 and 2004 together
Thanks again

 

[a a r o n _ k e m p f]

you should keep your data in SQL Server, then you can share it between
2000, 2002, 2003 and 2007 without a problem