When trying to open a MS Access 2003 application, it appears that the
application is generating a message box with an application specific
error. This error appears to indicate that some hardcoded path to
another access db is invalid. The error trap will not allow the
application to go any further and does not open the visual basic editor
to allow viewing the application code so that it can be fixed. The
only way out of this situation is to kill Access with the task manager.

I verified that the path indicated in the message box is invalid by
using a hex editor and looking at the specified path value.

Is there a way to specify MS Access is to start in debug mode so that
we can step and break execution and fix the hard coded info?

Thanks in advance!

Mark

Hold down the shiftkey while you open the database. Then go to Tools,
Linked Table Manager; put a check at the bottom, select all tables and
locate the backend mdb. Sounds like the backend mdb was moved.

--
Joan Wild
Microsoft Access MVP

(E-Mail Removed) wrote:
> When trying to open a MS Access 2003 application, it appears that the
> application is generating a message box with an application specific
> error. This error appears to indicate that some hardcoded path to
> another access db is invalid. The error trap will not allow the
> application to go any further and does not open the visual basic
> editor to allow viewing the application code so that it can be fixed.
> The only way out of this situation is to kill Access with the task
> manager.
>
> I verified that the path indicated in the message box is invalid by
> using a hex editor and looking at the specified path value.
>
> Is there a way to specify MS Access is to start in debug mode so that
> we can step and break execution and fix the hard coded info?
>
> Thanks in advance!
>
> Mark

Thanks, Joan, but this did not work. Holding the shift key while
opening the db puts me in the same spot as before. Is there anything
that might make this situation unique?

Thanks,
Mark.


Joan Wild wrote:
> Hold down the shiftkey while you open the database. Then go to Tools,
> Linked Table Manager; put a check at the bottom, select all tables and
> locate the backend mdb. Sounds like the backend mdb was moved.
>
> --
> Joan Wild
> Microsoft Access MVP
>
> (E-Mail Removed) wrote:
> > When trying to open a MS Access 2003 application, it appears that the
> > application is generating a message box with an application specific
> > error. This error appears to indicate that some hardcoded path to
> > another access db is invalid. The error trap will not allow the
> > application to go any further and does not open the visual basic
> > editor to allow viewing the application code so that it can be fixed.
> > The only way out of this situation is to kill Access with the task
> > manager.
> >
> > I verified that the path indicated in the message box is invalid by
> > using a hex editor and looking at the specified path value.
> >
> > Is there a way to specify MS Access is to start in debug mode so that
> > we can step and break execution and fix the hard coded info?
> >
> > Thanks in advance!
> >
> > Mark

Are you holding down the shiftkey (and continuing to hold it) until the mdb
opens? If so, then perhaps the shiftkey bypass was disabled. Try enabling
it again. Look for By Pass Shift Key Code at
http://www.members.shaw.ca/AlbertKal.../msaccess.html



--
Joan Wild
Microsoft Access MVP

(E-Mail Removed) wrote:
> Thanks, Joan, but this did not work. Holding the shift key while
> opening the db puts me in the same spot as before. Is there anything
> that might make this situation unique?
>
> Thanks,
> Mark.
>
>
> Joan Wild wrote:
>> Hold down the shiftkey while you open the database. Then go to
>> Tools, Linked Table Manager; put a check at the bottom, select all
>> tables and locate the backend mdb. Sounds like the backend mdb was
>> moved.
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> (E-Mail Removed) wrote:
>>> When trying to open a MS Access 2003 application, it appears that
>>> the application is generating a message box with an application
>>> specific error. This error appears to indicate that some hardcoded
>>> path to another access db is invalid. The error trap will not
>>> allow the application to go any further and does not open the
>>> visual basic editor to allow viewing the application code so that
>>> it can be fixed. The only way out of this situation is to kill
>>> Access with the task manager.
>>>
>>> I verified that the path indicated in the message box is invalid by
>>> using a hex editor and looking at the specified path value.
>>>
>>> Is there a way to specify MS Access is to start in debug mode so
>>> that we can step and break execution and fix the hard coded info?
>>>
>>> Thanks in advance!
>>>
>>> Mark

Thanks, Joan!! That advice did the trick. I'm now able to open, edit
and fix the problem.

Mark


Joan Wild wrote:
> Are you holding down the shiftkey (and continuing to hold it) until the mdb
> opens? If so, then perhaps the shiftkey bypass was disabled. Try enabling
> it again. Look for By Pass Shift Key Code at
> http://www.members.shaw.ca/AlbertKal.../msaccess.html
>
>
>
> --
> Joan Wild
> Microsoft Access MVP
>
> (E-Mail Removed) wrote:
> > Thanks, Joan, but this did not work. Holding the shift key while
> > opening the db puts me in the same spot as before. Is there anything
> > that might make this situation unique?
> >
> > Thanks,
> > Mark.
> >
> >
> > Joan Wild wrote:
> >> Hold down the shiftkey while you open the database. Then go to
> >> Tools, Linked Table Manager; put a check at the bottom, select all
> >> tables and locate the backend mdb. Sounds like the backend mdb was
> >> moved.
> >>
> >> --
> >> Joan Wild
> >> Microsoft Access MVP
> >>
> >> (E-Mail Removed) wrote:
> >>> When trying to open a MS Access 2003 application, it appears that
> >>> the application is generating a message box with an application
> >>> specific error. This error appears to indicate that some hardcoded
> >>> path to another access db is invalid. The error trap will not
> >>> allow the application to go any further and does not open the
> >>> visual basic editor to allow viewing the application code so that
> >>> it can be fixed. The only way out of this situation is to kill
> >>> Access with the task manager.
> >>>
> >>> I verified that the path indicated in the message box is invalid by
> >>> using a hex editor and looking at the specified path value.
> >>>
> >>> Is there a way to specify MS Access is to start in debug mode so
> >>> that we can step and break execution and fix the hard coded info?
> >>>
> >>> Thanks in advance!
> >>>
> >>> Mark