Problems with Developing in Access 2007 for 2003 client

[Cynthia]

I am currently developing a db for a client who is using 2003 and will not be
upgrading to 2007 in the forseeable future. I plan to develop in 2007 and
save as a 2003-2003 database and test in 2003.

I am interested to hear if anyone has any encountered any problems with this
scenerio or has any thoughts as to why I should not do this. While I have
two PCs, one loaded with Access 2003 and the other 2007 I really enjoy
working in 2007.

 

[Hans Up]

I am currently developing a db for a client who is using 2003 and will not be
upgrading to 2007 in the forseeable future. I plan to develop in 2007 and
save as a 2003-2003 database and test in 2003.

I am interested to hear if anyone has any encountered any problems with this
scenerio or has any thoughts as to why I should not do this. While I have
two PCs, one loaded with Access 2003 and the other 2007 I really enjoy
working in 2007.

I received an Access database which was created with 2007, and saved in
2002-2003 format. When I opened it with Access 2003, Access crashed
shortly after I opened a form (the type of crash where it offers to send
a report to Microsoft). Among the problems I discovered was it used a
constant which is not available in 2003.

You can see another example of that type of incompatibility if you
search this group for acViewReport.

If you have a solid grasp of which 2007 features are not available in
2003, and scrupulously avoid them, your approach is fine. However, it
would be safer to test the application rigorously with 2003 before
sending to your client.

Good luck,
Hans

 

[Cynthia]

Thanks, I'll do a search for acViewReport

 

[Hans Up]

Thanks, I'll do a search for acViewReport

The one I had in mind was near the end of March, in a thread with
Subject: Report "List".

Hans

 

[Paul Shapiro]

I did that for a couple of years, with the only significant problem being a
problematic interaction with SourceSafe. If you're not using source code
control, you should be ok. If you are using source code control, definitely
post back and I'll give you the summary of the issues I had and the
work-arounds.

I would not convert the database to Acess 2007 format. Keeping it in Access
2003 format while you work in Access 2007 avoids the need for any conversion
and mostly prevents you from using incompatible features. Before
distributing to the client, open it in Access 2003. Check the VBA references
for any marked MISSING and correct those for the Office 2003 references.
Make sure the application compiles, and it should be fine in Access 2003.

I found Virtual PC very convenient for doing the Access 2003 testing, rather
than a separate physical pc. If you're using Vista and the client is on
Windows XP, it's a good idea to use Windows XP for the test system. The
oldest client OS and the oldest client Office version is the best
compatibility test.