B
BogMonster via AccessMonster.com
Hi,
I have an unusual problem that I hope somebody can help me with.
I have a form with a Microsoft Office Spreadsheet 10.0 control on it. It's
from the MS Office Web Components library "OWC10" and is usually used to
publish Excel spreadsheets to data access pages or web. However, it's perfect
for my requirements in an Access 2002 form.
I have a procedure that manipulates the control to format it as required.
Basically it pulls data from a couple of tables and writes the data to
various cells, formats it as required, locks cells as required etc. The
procedure runs fine, no errors thrown up. All errors are trapped and would be
written out to the debugger. The resulting spreadsheet works just as I need
it too, but the catch is that I have to shut down Access first!
After the procedure runs, I can no longer open any tables or forms and even
trying to open the Linked Table Manager from Utilities throws the mesage [The
Microsoft Jet database engine could not find the object ". Make sure the
object exists etc....]. Normally this type of message names the missing
object but this just says ". in the message. If I close the database window,
not Access, and try to open ANY mdb database file I get the message
[Microsoft Access was unable to create the Database window. Please upgrade to
a newer version of Microsoft Internet Explorer." and then it promptly shuts
the window down. BTW, I have IE6 installed!
Once I close the Access application, I can reopen and everything is peachy.
The control that was originally manipulated by my procedure looks fine and
works perfectly (proving the procedure completed correctly!). In fact, it's
pivotal to the whole client side database. So I could work around this by
warning the user prior to the procedure running and afterwards closing Access
programmatically so that it looks controlled. The control should not require
frequent redrawing, maybe once a month. However, I would prefer not to have
to do this, especially when I don't know why it happens.
Has anybody experienced this or has some insight into this bizarre behaviour?
Thanks.
I have an unusual problem that I hope somebody can help me with.
I have a form with a Microsoft Office Spreadsheet 10.0 control on it. It's
from the MS Office Web Components library "OWC10" and is usually used to
publish Excel spreadsheets to data access pages or web. However, it's perfect
for my requirements in an Access 2002 form.
I have a procedure that manipulates the control to format it as required.
Basically it pulls data from a couple of tables and writes the data to
various cells, formats it as required, locks cells as required etc. The
procedure runs fine, no errors thrown up. All errors are trapped and would be
written out to the debugger. The resulting spreadsheet works just as I need
it too, but the catch is that I have to shut down Access first!
After the procedure runs, I can no longer open any tables or forms and even
trying to open the Linked Table Manager from Utilities throws the mesage [The
Microsoft Jet database engine could not find the object ". Make sure the
object exists etc....]. Normally this type of message names the missing
object but this just says ". in the message. If I close the database window,
not Access, and try to open ANY mdb database file I get the message
[Microsoft Access was unable to create the Database window. Please upgrade to
a newer version of Microsoft Internet Explorer." and then it promptly shuts
the window down. BTW, I have IE6 installed!
Once I close the Access application, I can reopen and everything is peachy.
The control that was originally manipulated by my procedure looks fine and
works perfectly (proving the procedure completed correctly!). In fact, it's
pivotal to the whole client side database. So I could work around this by
warning the user prior to the procedure running and afterwards closing Access
programmatically so that it looks controlled. The control should not require
frequent redrawing, maybe once a month. However, I would prefer not to have
to do this, especially when I don't know why it happens.
Has anybody experienced this or has some insight into this bizarre behaviour?
Thanks.