B
Bill Sturdevant
I have a front-end that links to a back-end database. If
the back-end database is unavailable, the main screen
opens anyway. (This is OK because I then let the user
pick the back-end they want and I link to it).
BUT, I have another front-end that links to a separate
back-end database. In this case, if the back-end is not
available, I get a message "C:\blah blah blah is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on
which the file resides." Then, when I click OK, the main
screen does NOT open.
I have been unable to determin what is different about the
two front-ends. They have the same AutoExec macros, and
are alike in all other respects. They have identical
settings in Startup and Options. What is different?
I want them to act like the first one. They used to act
like the firsst second one, but I did something to the
first one to change its behavior a couple of months ago,
but cannot remember what I changed.
Any help would be appreciated.
the back-end database is unavailable, the main screen
opens anyway. (This is OK because I then let the user
pick the back-end they want and I link to it).
BUT, I have another front-end that links to a separate
back-end database. In this case, if the back-end is not
available, I get a message "C:\blah blah blah is not a
valid path. Make sure that the path name is spelled
correctly and that you are connected to the server on
which the file resides." Then, when I click OK, the main
screen does NOT open.
I have been unable to determin what is different about the
two front-ends. They have the same AutoExec macros, and
are alike in all other respects. They have identical
settings in Startup and Options. What is different?
I want them to act like the first one. They used to act
like the firsst second one, but I did something to the
first one to change its behavior a couple of months ago,
but cannot remember what I changed.
Any help would be appreciated.