FAQ... Your questions will be
answered promptly as they come in.
Q: The Microsoft
Setup Wizard will not allow me to set a custom destination directory for
the EifG97 mde file. It acts like the only options are the build in App,
Win, or WinSys paths. What am I doing wrong?
good news is you are not going crazy!!! This is unfortunately a very bad
limitation of the MS Wizard which is why we seldom use it (unless distributing a
runtime app). With the wizard you can put it into the App, Win or Sys directory
only. The sequence of access to update references is: 1. it looks in the
specified dir of the reference; 2. then the application directory; 3. then the Access
directory. So by that logic do this: Copy the mde to your intended application
dir (C:\Program Files\Your Program Dir) then set the reference in your app to it. Run
your app to test it. Then redo your setup and place the mde in the appropriate
dir. Your only other alternative is to look into MS Access documentation to
learn how to pragmatically change the application references in code (yes, this
We handle this by
creating a Common File folder and install the MDE file
to it on the end users machine. That way the reference
will be found exactly where we expect it regardless of
where the end user decides to install the
application.. This will avoid any Microsoft automation
attempts to resolve the reference.
Setup program will not see my installation of Microsoft
Access. What am I doing wrong?
good news is you are not going crazy!!! On January 6, 2007 we updated the setup
to see Access 2003 version. However, you must know
that supported versions are Access 97/2000/XP....
However, we have 2003 customers that have reported
that the app runs fine with 2003.