R
Rick
I am having a heck of a time getting past my latest snag with ACC2007.
I have placed the full development environment on both my home (development
PC) and the target (Win2003 server). During prototyping I would place a copy
of the full <prom.accede> onto the server and the Users could test and send
me feedback. These iterations worked well until last week. Any new
<prom.accede> now however will not run and there are no messages saying what
the problem is. The db fails to start but the Access home page comes up.
That's it.
I have not made any changes that would affect references, table layouts,
etc. I can't even hold the shift key and bypass the start form.
Has anyone any ideas as to what may be happening? Or perhaps there is a
runtime switch which will force Access to get verbose?
Thanks for your help.
... rick
I have placed the full development environment on both my home (development
PC) and the target (Win2003 server). During prototyping I would place a copy
of the full <prom.accede> onto the server and the Users could test and send
me feedback. These iterations worked well until last week. Any new
<prom.accede> now however will not run and there are no messages saying what
the problem is. The db fails to start but the Access home page comes up.
That's it.
I have not made any changes that would affect references, table layouts,
etc. I can't even hold the shift key and bypass the start form.
Has anyone any ideas as to what may be happening? Or perhaps there is a
runtime switch which will force Access to get verbose?
Thanks for your help.
... rick