S
Susie
Hi...I have recently converted all of my databases
from '97 to XP. We have ongoing events that we just copy
a database for each new event. I have a macro that simply
outputs a file (daily)(in Rich Text Format) to a directory
to be uploaded to our intranet page. The macro runs fine
in '97, but since we have converted to XP, we get the
following message:
"Microsoft Access can't start the OLE server.
You tried to use a form, report, or datasheet that
contains an OLE object, but the OLE server (the
application used to create the object) may not be
registered properly. Reinstall the OLE server to register
it correctly."
We tried the macro with the output format in Snaphot
Format, and that format seems to work (however, we do not
want to use that format). But when we switch back to Rich
Text, it gives us that message.
I have talked to our Help Desk, and they have assured me
that everything is installed correctly. I have tried to
compact and repair the database, I have tried to rewrite
the macro in the XP version. I have changed the output
location from our server to my local drive, still with the
same error.
Our help desk suggested the database may be corrupted, but
this is happening in all of our XP databases, even the
ones we have created in XP (no copying from '97
involved). Any suggestions would be greatly appreciated.
Thank you,
Susie
from '97 to XP. We have ongoing events that we just copy
a database for each new event. I have a macro that simply
outputs a file (daily)(in Rich Text Format) to a directory
to be uploaded to our intranet page. The macro runs fine
in '97, but since we have converted to XP, we get the
following message:
"Microsoft Access can't start the OLE server.
You tried to use a form, report, or datasheet that
contains an OLE object, but the OLE server (the
application used to create the object) may not be
registered properly. Reinstall the OLE server to register
it correctly."
We tried the macro with the output format in Snaphot
Format, and that format seems to work (however, we do not
want to use that format). But when we switch back to Rich
Text, it gives us that message.
I have talked to our Help Desk, and they have assured me
that everything is installed correctly. I have tried to
compact and repair the database, I have tried to rewrite
the macro in the XP version. I have changed the output
location from our server to my local drive, still with the
same error.
Our help desk suggested the database may be corrupted, but
this is happening in all of our XP databases, even the
ones we have created in XP (no copying from '97
involved). Any suggestions would be greatly appreciated.
Thank you,
Susie