Hi Jerry
Take a look at Richard's Access Developer 33. I think that will help you

John

I do this in the ABCD and the Account Balances databases too.

The trick here is to know where the back end (BE) is.
There are a lot of little things I need to know before a user logs in.
A lot of these can change based on who and where the user is, like language or currency.
For the dozen or so of these parameters that need to be "fed" into the front end (FE) there are two choices:
1) Put the path to the BE in a control table in the FE. But then everyone that gets that FE needs to have the same BE path, which isn't too unreasonable.
2) At FE startup (like login) read a text file with this BE path (and any other parameters) that are needed to get the ball rolling.

Here's a sample of the code I use:

<CODE>
  FileNm = CurrentProject.Path & "\sbda.txt"
  iFile = FreeFile

  Open FileNm For Input As #iFile
  lcnt1 = 1
  Do Until EOF(1) Or lcnt1 > 12
    Line Input #1, temp1
    mSp(0, lcnt1) = temp1
    lcnt1 = lcnt1 + 1
  Loop
  Close #iFile
</CODE>

Thanks for the help.  Problem solved