 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Multiuser / Networking / August 2004Multi-user installations
I am working with a large database which is used by many, many external organisations. These organisations all return data from this database to ourselves. The database is very often used in a multi-user environment with the front end being placed on individual computers and the back-end on a server. At present we trail around the city installing this database for the organisations concerned. It seems to me that this cannot possibly a sensible way of doing things. Can anybody experienced offer any advice on how they would approach the situation? It does not really seem possible to just send out a disk because everybody's backend is in a different location. Moreover, one always has to make the link to that backend. As far as I am aware there is no way to automate that procedure but perhaps somebody knows different? You might want to consider making installation files. InnoSetup is a good way to do this: http://www.jrsoftware.org/isinfo.php . You could make a different setup file for each customer if you wish. You also might want to take advantage of Tony's AutoFEUpdater: http://www.granite.ab.ca/access/autofe.htm This utility can help you make links to a back-end database: http://www.peterssoftware.com/tlk.htm Hope this helps, Peter De Baets Peter's Software - MS Access Tools for Developers http://www.peterssoftware.com > I am working with a large database which is used by many, many external > organisations. These organisations all return data from this database to [quoted text clipped - 7 lines] > one always has to make the link to that backend. As far as I am aware there > is no way to automate that procedure but perhaps somebody knows different? Here's how I do it. I created a .ini file which holds the path of the backend data file. On opening the database, the program then reads the .ini file to get the location of the backend. Then, I relink all of the tables. Works completely reliably for me. Then, whenever a front end update is needed, they simply download it from my ftp server and they are back up with the latest version. Hope this is what you were looking for. >I am working with a large database which is used by many, many external > organisations. These organisations all return data from this database to [quoted text clipped - 13 lines] > there > is no way to automate that procedure but perhaps somebody knows different? Dan I was wondering how you relink the tables? Are you doing that via code? TIA Michelle **please only post replies to group** > Here's how I do it. > I created a .ini file which holds the path of the backend data file. [quoted text clipped - 23 lines] > > there > > is no way to automate that procedure but perhaps somebody knows different? There is example code in the Solutions sample database. It's on the distribution media (diskettes or CD) for Access 97 and earlier, and, for Access 2000 and later, temporarily housed at http://www.mvps.org/access/downloads/bapp2000.exe until it gets put back on the Microsoft website. Larry Linson Microsoft Access MVP > Dan > [quoted text clipped - 35 lines] > > > is no way to automate that procedure but perhaps somebody knows > different? Thanks Larry > There is example code in the Solutions sample database. It's on the > distribution media (diskettes or CD) for Access 97 and earlier, and, for [quoted text clipped - 47 lines] > > > > is no way to automate that procedure but perhaps somebody knows > > different? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.