S
Scott McDaniel
Thanks for reading this.
I've built a database using Access 2002 with the Access 2000 format. I've
compiled, then compacted/repaired, and then used Wise Installation Systems
to build my deployment package. I have the standard references, including
DAO and ADODB, with 3 other references - FMS Total Memo Control 2002, Mabry
TreeX, and CSMail. All three are declared compatible with Access 97 or
better. I also distribute two INI files, and 2 text files. All .ocx files
are registered, and I've verified that the references are, in fact, set and
referenced on my target machine.
I can deploy this package with an .mdb file, install it on my test platform
(vmWare Workstation with a "virgin" installation of Windows 2000 and Access
2000) and it will relink the tables on a network drive and run fine. I can
navigate my menus, open forms, print reports, blah blah blah
Back at my development machine, if I make my .mdb into an .mde file and do
the same deployment - substituting my .mde file for the .mdb file - then my
app installs correctly, relinks the tables ... but I get this error when
attempting to open my a form:
MSAccess.exe exception: The instruction at at xxxx referenced memory at xxx.
Memory could not be "written".
The numbers change from time to time, but the error is always the same.
However, the exact same database (an .mdb, not an .mde) will run perfectly
fine if I simply copy it from my development machine to the vmWare instance
.... I've tried making my .mde file on the vmWare instance, then copying that
file back to the development machine, making my deployment package, then
re-deploying it WITH the .mde that was created on the vmWare instance, and
the same thing happens.
Any ideas? I wrote a small utility that "read" the references in the .mde
file on the vmWare machine, and all references were as expected. I even
moved one of my reference files and re-registered it to see if the .mde file
would pick it back up (it did).
Interestingly enough, if I build a shortcut with the /compact switch and run
this immediately before opening the database, the problem seems to go away
until your reboot the vmWare instance.
Note also that this behaviour is also noted by at least one other person
working on a remote machine ... I deployed the install package to them today
(with the .mde file), and they reported the same behaviour
--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP
"Smash forehead on keyboard to continue ... "
I've built a database using Access 2002 with the Access 2000 format. I've
compiled, then compacted/repaired, and then used Wise Installation Systems
to build my deployment package. I have the standard references, including
DAO and ADODB, with 3 other references - FMS Total Memo Control 2002, Mabry
TreeX, and CSMail. All three are declared compatible with Access 97 or
better. I also distribute two INI files, and 2 text files. All .ocx files
are registered, and I've verified that the references are, in fact, set and
referenced on my target machine.
I can deploy this package with an .mdb file, install it on my test platform
(vmWare Workstation with a "virgin" installation of Windows 2000 and Access
2000) and it will relink the tables on a network drive and run fine. I can
navigate my menus, open forms, print reports, blah blah blah
Back at my development machine, if I make my .mdb into an .mde file and do
the same deployment - substituting my .mde file for the .mdb file - then my
app installs correctly, relinks the tables ... but I get this error when
attempting to open my a form:
MSAccess.exe exception: The instruction at at xxxx referenced memory at xxx.
Memory could not be "written".
The numbers change from time to time, but the error is always the same.
However, the exact same database (an .mdb, not an .mde) will run perfectly
fine if I simply copy it from my development machine to the vmWare instance
.... I've tried making my .mde file on the vmWare instance, then copying that
file back to the development machine, making my deployment package, then
re-deploying it WITH the .mde that was created on the vmWare instance, and
the same thing happens.
Any ideas? I wrote a small utility that "read" the references in the .mde
file on the vmWare machine, and all references were as expected. I even
moved one of my reference files and re-registered it to see if the .mde file
would pick it back up (it did).
Interestingly enough, if I build a shortcut with the /compact switch and run
this immediately before opening the database, the problem seems to go away
until your reboot the vmWare instance.
Note also that this behaviour is also noted by at least one other person
working on a remote machine ... I deployed the install package to them today
(with the .mde file), and they reported the same behaviour
--
Scott McDaniel
CS Computer Software
Visual Basic - Access - Sql Server - ASP
"Smash forehead on keyboard to continue ... "