Access Front End

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have split my application to FE and BE. The BE (database) is sitting in a file server while FE will be local LAN users or VPN remote users

I have 3 questions
1. Is there any problem for VPN remote users connecting to the database
2. If I want to move the BE to another server, what should I do? Can I change the path within the FE
3. How does FE know the path of the BE

The following are the step I splitted the application
1. I copy the application from a development PC to the server
2. I use Database Splitter to split the FE
3. Copy the FE and paste it to other front end machines.
 
----- WC Lo wrote: ----

I have split my application to FE and BE. The BE (database) is sitting in a file server while FE will be local LAN users or VPN remote users

I have 3 questions
1. Is there any problem for VPN remote users connecting to the database

R: If yopu have the db in a networked drive you should better use the absolute path in the front end. That's: \\computername\share_name\be_file_name

2. If I want to move the BE to another server, what should I do? Can I change the path within the FE

R: Change the Within in the FE

3. How does FE know the path of the BE
R: Through the linked table manager
 
WC Lo said:
After I change the path with Link Manager, can I make the FE as a MDE
file?

Yes...you can change the links via code, or the linked table manger in a
mdb, or mde.

Yes...if you make a mde (and you should)..that mde will have the same
settings as the original mdb (that you just set/changed).

In fact, most of us developers add some code to allow linking of tables in
case the location is changed.

So, often, right before I make the mde file...I re-link my mdb to the "main
production" back end...(not the one that I was ust using for testing of some
big delete rouinte for example!!!). So, I re-link the mdb to the correct
back end...run it to make sure it works..and then create the mde for people
to use...
 
Back
Top