Access 2007 DB and VPN issues

[S.Hanagan]

I have a frontend and backend database installed at my office. I (used to)
do most of my programming on the front end while at home by linking the home
db to duplicate tables at home. However, after I split the database at my
office I am no longer able to even open the front end portion of the database
existing on my home computer. The program quickly just compacts and closes
again, never even opening the DB.

Any thoughts on what is going on here would be greatly appreciated.

 

[David C. Holley]

Do you have any code that runs on startup?
(Rules out any issues related to startup-code)

Have you tried creating a new front end and connecting to the MDB on your
org's file server?
(Confirms that you're able to link to the back end and see the data)

Have you tried opening the backend via the VPN?
(Confirms that you're able to access the backend as a file)

 

[S.Hanagan]

Sorry to answer in reverse order, but I suspect the solution lies in the
startup issue you asked about. Yes I can split the db and link to it on the
office setup. I can also open the backend directly from my home machine.
Only problem is the frontend on my home machine (copied over from a running
office machine) won't even start up while at home.

Do you have any code that runs on startup?
(Rules out any issues related to startup-code)

Yes, there is an autoexec macro that runs (all macros are enabled on the
DB). The autoexec reads some start up variables from the BE. I mannually
split the DB (am not using Allan Browns programatic link table manager).
After the split, I checked the BE via the linked table manager and confirmed
that I used UNC connections as opposed to a simple drive letter.

I will disable the autoexec process for the home machine and see whether it
at least allows me to start the frontend of the database at home in order to
narrow this issue down a bit. This same setup worked in Access 2003,
although the linked tables had to be relinked to the duplicate BE on the home
machine.

Incidentally, it is an ACCDB backend rather than MDB, but I assume that is
simply a result of this being Access 2007 versus 2003.

 

[S.Hanagan]

Problem fixed.

My solution was to disable a portion of the startup code so that a couple of
reports I have don't run on the machine that is on a different node. Not
sure why that worked, but I mention it in case someone else runs across this
problem.