Thanks Aaron: So, then, the code blocks that references the ini file in a GW
script are not executed under a production situation? I am reading up on the
standard assignments and the use of the SharedObjects stuff. If the code is
executed but the ini file is not available does the code just return some non
critical value?
Rick USA
----- Original Message -----
From: Aaron Smith
To: gw-scripting@gwmicro.com
Sent: Tuesday, June 29, 2010 10:39 AM
Subject: Re: Missing ini file in GW msaccess script?
INI files are often used to store specific script settings, so you wouldn't
ship one with your package, only to end up overwriting a user's existing
settings. So the INI files referenced in most GW Micro scripts are created when
needed.
Aaron
On 6/29/2010 10:34 AM, RicksPlace wrote:
Hi:
I can not figure out where the msaccess.ini file might be for the following
senario.
Can you help?
I Installed the msaccess script by GW Micro using Jamal's Installer.
The 2 following files were installed:
msaccess.vbs
msaccess.xml
Inside the .vbs script it references a .ini file which was not included in
the
download and install.
Here is some of the code referencing the .ini file:
Dim myINIFile : myINIFile = ClientInformation.ScriptPath & "\msaccess.ini"
SO_StandardHelpDialog.INIFileName = myINIFile
SO_StandardHelpDialog.HelpTitle =
...
Also it is referenced here:
' Change ClientInformation.ScriptHelp to our real routine
ClientInformation.ScriptHelp = "ScriptHelp"
Else
' If Automatic_Update exists in our INI, and the value is 1, then
' we'll attempt to check for a new version.
If IniFile(myINIFile).Number("Automatic_Updates", "OnScriptStart") =
1 Then
...
Is there suppose to be a .ini file in the Downloaded package?
If not, what happens in a script when the reference is not found?
Rick USA
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
