Access2007 "Document ... caused a serious error"

[Rick]

I have Access2007 running on a Terminal Services server (Win2003 R2) within
my SBS domain. The SBS holds the BE tables and the TS holds the FE database.
The db is an .accede.

I get an error message upon opening the FE "The document <dbname> caused a
serious error the last time it was opened. Would you like to continue?
Yes/No."

I always chose Yes. Interesting thing is this message only happens every 2nd
time. The DB is in testing at the moment and I am the only user so it has
nothing to do with record locking. Also, I am running as a domain admin and
have 'full' security permissions on the folders.

I have looked at the Events for Access and the database closes properly
every time.

The FE is placed in a folder on C:/DBNAME and this folder is Trusted in
Access.

I have brought in a new version from my development machine, followed the
MSoft procedure by going to the COM Add-In as per the instruction (there are
no 'problem' documents). Every time it runs it acts normal.

Is there a registry entry somewhere that is getting turned on/off after each
run?

This thing is driving me nuts.

Any help would be greatly appreciated.

Thanks.

... Rick

 

[Allen Browne]

First thing would be to make sure Compact On Close is *off*.
In A2007, it's under Office Button | Access Options | Current Database.
(While you're there, make sure the Name AutoCorrect options are off also.)

I'm not completely clear about whehter C:\DBName is on the TS server?
If so, are multiple people opening the same front end file?

Of is C:\DBName on the workstation, in which cace TS is opening it across
the network (not recommended.)

 

[Rick]

Thanks, Allen.

Yes. compact on close is off and so are autocorrect options.

Yes, the C:\DBName is the FE on the TS server and yes, multiple people (will
be) opening it at the same time. But if all the tables are removed
(including the MsSys tables) why shouldn't they run from one copy of the
code?

Also, the BE is on the SBS server so it is being accessed across the LAN.

BUT, at the moment I am the ONLY one running it so I can't see any issues
with record locking, table contentions, data corruption, etc. It is just
this weird security issue that happens every 2nd time I run.

.... rick

 

[Allen Browne]

Perhaps others can contribute suggestions. I don't use Terminal Server much.

Separate front ends certainly solves some concurrency issues. However, if
you are the only one using it, and opening only one copy, then I doubt it's
a concurrency issue. Perhaps there is something else going on, e.g.
something being instantiated that is not correctly cleaned up.