Access 2007 vs 2003

T

Todd C

I was using Access 2003 for many years and have developed some ADP/ADE
applications for our users. I recently upgraded to Office 2007.

Now, after Access 2007 has opened a .ADP file and I have made a .ADE
exetension of it for the users, even though the original is "Access 2002-2003
file format", the users cannot open the ADE with Access 2003.

So I figured I would install Access 2003 as well, and generate the ADE that
way. But not Access 2003 CANNOT OPEN the original file, EVEN THOUGH it is
flagged as 2003 format!

Even more: If I right-click on the file and select "Open with Access 2003",
it goes into it's "Configuring office 2003" routine. When that is done, it
tells me that the file is not in the right format. After that,
double-clicking on that file will make Access 2003 come up.

If I do the same thing again but choose to "Open with ... Access 2007" then
THAT program goes into ITS "Configuring Office 2007" routine and every
double-click after that makes Access 2007 launch.

WHAT THE %$#@*& IS GOING ON?

Access 2007 is NOT compatible with Access 2003, REGARDLESS OF what the File
Type says.
AND, I SHOULD BE GIVEN CONTROL OVER WHAT PROGRAM IS GOING TO OPEN ANY FILE
TYPE. IF I HAPPEN TO SELECT THE "Open with" AND CHOOSE A DIFFERENT PROGRAM
THIS TIME AROUND, IT DOES NOT MEAN THAT I WANT TO USE THAT PROGRAM ALWAYS.

WHEN IS MICROSOFT GOING TO PUT CONTROL BACK IN THE USER'S HANDS??

Now, I'm STUCK with a file that is NOT backward compaitble for my users and
myself.
 
H

Harlan Grove

Todd C said:
I was using Access 2003 for many years and have developed some
ADP/ADE applications for our users. I recently upgraded to Office
2007.
Click to expand...
....

If you want to rant, fine, but if you want any advice about the
problem, THIS is definitely NOT the right newsgroup. Few experienced
Access users or developers respond in this
 
H

Harlan Grove

Todd C said:
I was using Access 2003 for many years and have developed some
ADP/ADE applications for our users. I recently upgraded to Office
2007.
Click to expand...
....

If you want to rant, fine, but if you want any advice about the
problem, THIS is definitely NOT the right newsgroup. Few experienced
Access users or developers respond in this newsgroup, so you'd be
better off posting in an Access-specific newsgroup.

And, FWIW, I know what you mean. I work mostly with Excel. The new
worksheet grid now provides a number of cells beyond the capacity of
long integers, so the .Count property of the range class could now
throw errors for large ranges. MSFT did provide a new .CountLarge
property with a data type that can accommodate the new grid size, but
it means adding conditional blocks to existing VBA code to check for
Excel version and changing the data types of all variables that might
ever need to hold a new grid's cell count. Unpleasant, but there *IS*
a way to have one code base work with Excel 2007 and prior versions
back to Excel 2000 (back to Excel 97 gets into VBA5 vs VBA6 issues).

There may be similar unpleasant but possible approaches for dealing
with Access and ADP/ADE. But if there are, you'd need to look for them
in Access-specific newsgroups.
 
Top