B
Boyd Trimmell aka HiTechCoach
I have seen posts where people say that you can use Access 2007 to run MDE's
created with previous versions of Access. Unfortunately, that has not been my
experience. It only seems to work with MDB's only.
Here is what I found using Access 2007 SP2. Testing with both the full and
runtime versions on different machines:
* Can open the MDB and everything runs fine.
* Take the same working MDB and create an MDE with Access 2003 SP3 on
development machine. Deploy to the Access 2007 machines. Get library errors.
Can't find Trim(), etc. I have this issue with all of my databases.
It appears that the MDB, since not locked, will have the libraries converted
to the Access 2007, but the MDE will not.
I do have the DAO 3.6 library reference set in all my databases (MDE's).
Could this be the issue?
I have been working on this for a while now. I have to install the 2003
runtime to get around this.
Is there some way to use an 2003 created MDE with Access 2007? What am I
missing here?
Any suggestions?
created with previous versions of Access. Unfortunately, that has not been my
experience. It only seems to work with MDB's only.
Here is what I found using Access 2007 SP2. Testing with both the full and
runtime versions on different machines:
* Can open the MDB and everything runs fine.
* Take the same working MDB and create an MDE with Access 2003 SP3 on
development machine. Deploy to the Access 2007 machines. Get library errors.
Can't find Trim(), etc. I have this issue with all of my databases.
It appears that the MDB, since not locked, will have the libraries converted
to the Access 2007, but the MDE will not.
I do have the DAO 3.6 library reference set in all my databases (MDE's).
Could this be the issue?
I have been working on this for a while now. I have to install the 2003
runtime to get around this.
Is there some way to use an 2003 created MDE with Access 2007? What am I
missing here?
Any suggestions?