Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Wanet Telecoms Ltd on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Splitting the database

Status
Not open for further replies.

Vandys

IS-IT--Management
Aug 3, 2000
29
AU
I have split my application and created 2 files. I have also created a .MDE. Now I have to install this application on the user's unit. Do I have to relink the tables when the location of the database changes? How can I avoid this coz the user is in a different location and I wish to avoid going there for the installation.<br><br>Please advise.<br><br><br>Vandys
 
You will have to re-link if the paths are different, so:<br><br>Put the database in the same location on their machine as it is on yours. For example, if your database in in C:\My Documents\Databases, then create the same folders on their machine. Then when you link the tables on your machine, the paths will be the same on the user machine. Or it could be as simple as putting it on the C:\ root drive, and then you know it will link on any machine.<br><br>Now if they are on a network, you can just link to a network location, and it should work on both machines. <p>Jim Lunde<br><a href=mailto:compugeeks@hotmail.com>compugeeks@hotmail.com</a><br><a href= Application Development
 
Thanks Jim,<br><br>I am sure this will work . But the user wishes to put the application on the network( for ex. s:\trip\tripdb\). But I am not on the same network. Is there a way that I can do a linking by mentioning the path as above and then send across the application to the user?<br><br>Vandys
 
One suggestion is to create a local mapping on your p.c. In a DOS session type in &quot;subst s: c:\trip\tripdb&quot;. As far as your front end is concerned you can link to your s drive which is really on your local drive. When you send the app to the user the front end will be pointing at his network drive.
 
Thanks a lot! This is a good suggestion. But, please tell me how to undo this dos command after I am through with this project.<br><br>Thanks again, your suggestion is a big help.<br><br>Vandys<br>
 
Hi Vandys,<br>To get rid of the virtual drive type in the following<br>&quot;subst s:/d&quot;<br><br>If you need to distribute your app to different users with different drive mappings you could have a small batch file for each virtual drive you need and a batch file to rid yourself of them when finished!
 
Use the table Link Manager to changes the links to the corresponding network links.&nbsp;&nbsp;In reality it serves no purpose to split a database unless you are going over the network.&nbsp;&nbsp;<br><br>Wushutwist
 
Thanks a lot all of you! All your suggestions were a great help. By the way, I noticed that the virtual drive type declared gets automatically cleared/deleted when the system is rebooted. I wish to split the Database coz the application will be ultimately put on the network. <br><br>Any suggestions about how to automatically link the tables if the location of the database is changed? <br><br>Vandys
 
I have found this thread in my quest to understand how i am going to get my database from London to be accessable in our branches in South Africa, Riga, and Dubai. I have tried the database splitter, but it comes up with errors, and states - 'Subscript out of range' and 'error occuring while copying relationships'

NOw, i have taken note of this thread and i think i have a good idea about how to go about it when it works. But, i need a little more advice with regards to getting hte front end up and running. will i have to go to these places to copy over the front end and set it up with links to the back end on the server? Thank you for your help already.

Matt Pearcey
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top