 |
| |
|
Initial Installation of StoreManager Offline
|
| |
|
Return to Online Manuals
|
| |
|
Subsequent Installation
|
| |
|
NB If you need any guidance on creating folders or copying files go to Using Windows Explorer
|
| |
|
Requirements
|
| = |
Operating System: Windows 2000 or XP
|
| = |
Excel: Version 10 (Office XP)
|
| = |
Word: Version 10 (Office XP)
|
| = |
Access: Version 10 (Office XP), with ActiveX controls turned on (these need to be turned on at the time of installation).
|
| = |
Ensure that C:\WINDOWS\SYSTEM32\comdlg32.ocx or C:\WINNT\system32\comdlg32.ocx exists.
|
| = |
Broadband Internet Access
|
| = |
Crystal Reports: Version 10 or higher
|
| = |
Internet Explorer: Version 5 or above
|
|
| |
|
Install mySQL ODBC drivers
|
|
A mySQL ODBC Driver acts as a translator between Store Manager Offline and the data you see in StoreManager Online.
|
|
The mySQL ODBC driver needs to be installed on all the machines StoreManager Offline will be used on.
|
|
The relevant files are on the CD you were given. Either MyODBC-3.51.11-2-win.exe or MyODBC-3.51.11-2-win.msi should work, but if one does not try the other.
|
|
The mySQL ODBC Driver does not yet work in a 64 bit operating system. So if the operating system on your machine is 64 bit, it is important for the system adminstrator to use the 32 bit ODBC administrator as opposed to the default 64 bit one to set up the DSNs.
|
|
You can see if it has already been installed if your ODBC Administrator shows MySQL ODBC 3.51 Driver on its list of drivers, when you click the Add button. For descriptions of how to find this Add button look under Create MySQL ODBC 3.51 Driver System DSN.
|
|
To install the mySQL ODBC Driver double click one of MyODBC-3.51.11-2-win.exe or MyODBC-3.51.11-2-win.msi and then follow the installation wizards instructions.
|
| |
|
Create MySQL ODBC 3.51 Driver System DSN
|
|
A DSN (Data Source Name) remembers where the data is and which driver should be used to talk to it.
|
|
If you are using standard 32 bit Windows, you open the ODBC Aministrator by clicking
Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). Then go to the System DSN Tab, and it should look like this.
|
|
Click Add
|
|
|
You will get this.
|
|
|
Then from the list pick “MySQL ODBC 3.51 Driver”, it is often right at the bottom, and click Finish
|
|
You will get a screen like this
|
|
|
Enter these values
|
| Data Source Name |
TacticSol
|
| Server |
212.100.249.5
|
| User |
TacticSol
|
| Password |
Telehone 08707 430043 or 01753 648800 during office hours
|
| Database |
Web
|
|
|
Click Test and you should get a message like this.
|
|
|
Click this OK, and the OK on Connector/ODBC Add Date Source Name and you will return to the ODBC Data Source Administrator Form showing the System DSN Tab.
|
|
Repeat this process from click Add but enter these values.
|
| Data Source Name |
SMOff
|
| Server |
85.189.118.209
|
| User |
SMOff
|
| Password |
Telehone 08707 430043 or 01753 648800 during office hours
|
| Database |
IVRWEB
|
|
|
You will need to create these DSNs on any machine you install StoreManager Offline on to.
|
| |
|
Copy Off CD
|
|
Copy StoreManagerData.mdb to a central location.
|
|
This could be on a networked server if several users are to be using the program, or on a user’s computer if only that user will be using the application.
|
|
Copy the following files to C:\StoreManager\StoreManager\ on the user’s computer.
|
|
CompanyCode.mdb
|
|
Spellcheck.doc
|
|
StoreActionSheet.rpt
|
|
StoreManager.ico
|
|
StoreManagerCode.mdb
|
|
StoreManagerTemp.mdb
|
|
Template JobData.xls
|
|
Anything like Template Worksheet.rpt EG Template COM Worksheet.rpt
|
| |
|
Recreate Link Tables
|
|
Open StoreManagerTemp.mdb and recreate all the linked tables with the same names to StoreManagerData.mdb. The tables must have names as listed below.
|
|
It is a good idea to delete all the linked tables before re-linking them. If you don’t do this, then Access will try to rename all the tables – for example tbl_Reps will become tbl_Reps1. If the tables are renamed like this, the program will not work.
|
|
Unless they have standardized their mappings, or StoreManager.mdb is on the machines own drive, make sure the link is in the format \\ServerName\ShareName\...\StoreManagerData.mdb
|
|
Tables which need to be recreated must have these exact names.
|
|
tbl_Brand
|
|
tbl_CancelledAllocation
|
|
tbl_Client
|
|
tbl_EPOS_Barcode
|
|
tbl_Glossary
|
|
tbl_Group
|
|
tbl_Issue_Resolution
|
|
tbl_Issue_Type
|
|
tbl_Job
|
|
tbl_Job_Prompts
|
|
tbl_Limits
|
|
tbl_Outlet
|
|
tbl_Outlet_Contact
|
|
tbl_Product
|
|
tbl_Rep
|
|
tbl_RepTitle
|
|
tbl_StoreAllocation
|
|
tbl_URN_Message
|
| |
|
Open StoreManagerCode.mdb and it should automatically update its tables from the ones you have just recreated in StoreManagerTemp.mdb.
|
|
Log in as you would to StoreManager Online.
|
| |
|
Suggestion
|
|
Once you have recreated the links in StoreManagerTemp.mdb, and StoreManagerCode.mdb has picked up these changes, during the installation on the first machine, copy these to a central location, with Spellcheck.doc, StoreActionSheet.rpt, StoreManager.ico, Template JobData.xls and Template Worksheet.rpt off the CD. Use these when you have to do subsequent installations, and you will not need to recreate the linked tables.
|
| |
|
Subsequent Installations
|
| |
|
Do not overwrite StoreManagerData.mdb as you will lose all the data you have already put in it.
|
|
CompanyCode.mdb contains code written specifically for you so do not overwrite it.
|
|
Copy the files listed here to C:\StoreManager\StoreManager\ overwriting older editions.
|
|
Spellcheck.doc
|
|
StoreActionSheet.rpt
|
|
StoreManager.ico
|
|
StoreManagerCode.mdb
|
|
StoreManagerTemp.mdb
|
|
Template JobData.xls
|
|
Anything like Template Worksheet.rpt EG Template COM Worksheet.rpt
|
| |
|
If a table in the list below does not exist in the StoreManagerData.mdb on your server open it and import the table(s) from the StoremanagerData.mdb on the CD.
|
| |
|
Recreate Link Tables
|
|
Open StoreManagerTemp.mdb and recreate all the linked tables with the same names to StoreManagerData.mdb. The tables must have names as listed below.
|
|
It is a good idea to delete all the linked tables before re-linking them. If you don’t do this, then Access will try to rename all the tables – for example tbl_Reps will become tbl_Reps1. If the tables are renamed like this, the program will not work.
|
|
Unless they have standardized their mappings, or StoreManager.mdb is on the machines own drive, make sure the link is in the format \\ServerName\ShareName\...\StoreManagerData.mdb
|
| |
|
Tables which need to be recreated must have these exact names.
|
|
tbl_Brand
|
|
tbl_CancelledAllocation
|
|
tbl_Client
|
|
tbl_EPOS_Barcode
|
|
tbl_Glossary
|
|
tbl_Group
|
|
tbl_Issue_Resolution
|
|
tbl_Issue_Type
|
|
tbl_Job
|
|
tbl_Job_Prompts
|
|
tbl_Limits
|
|
tbl_Outlet
|
|
tbl_Outlet_Contact
|
|
tbl_Product
|
|
tbl_Rep
|
|
tbl_RepTitle
|
|
tbl_StoreAllocation
|
|
tbl_URN_Message
|
| |
|
Open StoreManagerCode.mdb and it should automatically update its tables from the ones you have just recreated in StoreManagerTemp.mdb.
|
|
Log in as you would to StoreManager Online.
|
| |
|
Return to Online Manuals
|
| |
|
©Storecheck Marketing Ltd, 2007
|
|
No part of this document may be reproduced without express permission in writing from the Managing Director of Storecheck Marketing Ltd
|