Hello and welcome to our forums,
Thank you for your interest in Advanced Installer.
Below are the requirements, and I am stumped on the very first because the User’s Guide seems to indicate I must set up the ODBC by hard-coding the Ms-Acess database file path into the ODBC attributes - which will not do.
If you want to create a data source containing a database attribute pointing to your installed .mdb file then please note that you don't have to hard code the path to the Ms-Acess database file into the ODBC attributes.
The
Value field of an
attribute is of
Formatted Type for ODBC data sources and can be edited using
Smart Edit Control. You can
localize this value.
e.g. [#filekey] which means that the file references are replaced with the full path to the file on the target computer
1) At installation time the user must be able to select the directory for software installation and, optionally, a separate directory for the mdb. There need to be default directories for the locations of both the application and the mdb.
In order to achieve that you can create a
property based folder in the
Files and folders page where you add your .mdb file.
Property based folders will be resolved at install time to the values from the respective property. This property can be one of the Windows Installer
Folders, the result of a
Search operation or a custom property set in the
Install Parameters page.
You can add an
edit box where the user can set the installation path for the .mdb file and also use the
browse functionality.
2) If the specified mdb location already has an installed mdb, the new installation must NOT replace the database but simply set up the ODBC connection. This is important for situations where there are multiple users with the database installed on a server.
In order to achieve that you ca have custom search to see if the related file is already in that location, based on the user choice. Then you can perform the installation of that file only if in the selected folder there isn't an already a file with the same name.
3) When a user "uninstalls" the application using the Control Panel, the mdb must not be deleted.
In order to achieve that you can enable the
Permanent flag from the
component properties of the .mdb file in the
Organization page.
Also, I've attached a .zip archive which contains a sample which implement the custom directory selection and installation for the .mdb file and preventing the file to get deleted when the uninstall process is performed.
If you have other questions, please let us know.
Best regards,
Dan
FOLLOW US
Get the latest news in Application Packaging