VBA Project Explorer window

[Thomas Kroljic]

All,
I have an Access 2000 database (JET 3.6) on a Windows 2000 server. For
the past year the application has been rock solid. Lately, I've been
experiencing problems. 1) If I open a form in design mode and then click on
the icon in the toolbar to go into the vba code, my project explorer window
will not open up. If I select view/project explorer, nothing happens. I
then have to create a new database and import all the object.

2) I have a subform that keeps giving me "#error" message in all the
fields when the user exits the last field in the row. I also get this
strange record indicator to the left: a circle with a line through it. I've
check the code and it all looks good. This error/problem is not consistence.
It's just been happening on and off in the last month. I can create this
problem using the database on the server but I can not recreate this problem
with a copy of the database on my local PC.

any thoughts on either of these two problems?

Thank you,
Thomas J. Kroljic

 

[Sylvain Lafontaine]

Your the first one that I hear speaking of Access 2000 as "rock solid".

Try the /decompile parameter switch followed by a compact/repair instead of
importing all of your object into a new database. May help you saving some
time.

Your MDF file is located on a Windows 2000 server: if it is opened by more
than one strictly identical version of the operating system (for exemple,
WinXP vs WinMe or two WinXP with different service packs), even if not at
the same time, then this may be the source of the corruption of your
database. All users should open their own copy of the application on their
local machines; not from a server.

The indicator with a circle and a line indicate that the underlying record
has been locked with a pessimistic lock instead of an optimistic lock. With
Jet 3.6, locking one record in a pessimistic way may lead to multiple locked
records at the same time, as Jet make only paged locks, not record level
locks.

The "#error" may have many causes; one of them being the absence of a
primary key in your subform or the inability of Access to identify such a
key if your subform is based on too many joined tables. Record locking
problems can also be the source of this message.

S. L.

 

[Thomas Kroljic]

Sylvain,
Thanks for response. I am currently in the process of splitting the
database and creating separate frontends for each users. Both the FE and BE
databases will reside on a W2k server running Terminal Services. Hopefully
this will eliminate the database from potentially getting corrupted.

Thank you,
Thomas j. Kroljic