Corruption after switching from Novell to Citrix

G

Guest

For starters I learned what I know about Access on my own to build the
database I am writing about so my knowledge is minimal.

About 2 years ago I created an Access database which has worked great for
those 2 years until about a month ago when we switched from Novell to Citrix.
Ever since then the database 'corrupts' multiple times a day requiring all
users to exit then repair execution which seems to fix it temporarily. The
error says something like 'this is not a Microsoft Access database or the
data is corrupt'.

I tried moving the data to a copy I have but the problem continues so I feel
the problem is not with the database itself but with the change to Citrix. In
researching this I can see changing to Citrix could very well be the issue
because of multiple reasons.

My work environment is a large university campus so I have to work with our
computer support for any network or server issues and we have many people in
my department using the database who have already become frustrated with the
whole mess so I am asking for assistance in fixing this as efficiently as
possible. If someone can give me a list of sorts of everything I need to
change now that we use Citrix I would be extremely appreciative.

As I see it, there is an issue in the fact that I knew nothing about
splitting the database between front end and back end. Will that change alone
fix my problem? Is there an article on how to make that change?

Also apparently there is an issue with OpLocks? Is that always a problem or
only possibly? Some users may have switched to Windows XP or something. I am
not sure. Is fixing this extensive requiring help from my IT department?

I get the feeling there may be many more issues and would appreciate any
thoughts on possible problems. We are almost to the point of just trashing
the whole thing and trying to figure out a different application where our
medical clinics, spread out around the city, can share our call center's call
information instantaneously. Microsoft Access has worked beautifully until
now.

Please help.
Kristine
 
A

aaron.kempf

MDB isn't reliable enough for anything

you need to use SQL Server / Access Data Projects


ADP is much easier to learn than this MDB _CRAP_
MDB doesn't work for a half dozen users
 
A

aaron.kempf

you don't need to split it into frontend - backend

you just need to move to Access Data Projects
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top