Front End Corrupting

[dgm]

I have a database which about 10 people use pretty much all day.
It's set up so it uses a front end and a back end, and i had both the front end and backend on the server until recently.

Half the people are using it directly and the other half are using it via Citrix. Problem is the front end was/is being corrupted a couple of times per day. Through some code i discovered that it was always the citrix people that are corrupting it (although i can't narrow it down any further). So for the users not using Citrix i placed the front end on their local computers and it all works fine.

But the citrix users are still corrupting their copy and as they're not using a full desktop version of Citrix i was told they can't have a local copy for each user (i know very little about Citrix myself).

I just thought it was odd that it's the front end being corrupted as i always thought it was the tables that caused corruption? Does anyone know if there are certain actions that may increase the possiblity of corruption in a shared front end? Like changing the recordsource on a form or something like that? Or is it just Citrix that's causing the problem?

I'm currently working on upgrading the backend to sql server, but i'm not sure if this will help the corruption of the front end at all?

 

[Treason]

I think the whole point in splitting a DB into BE/FE is to allow a multi user evvironment. Otherwise you'll leave it all together and let everyone open it at once. I think your problem is sharing the front end. You have to force your users to install the front end locally, otherwise expect more corruption

 

[dgm]

I've created a user log so i know when people log on and off (or when they don't log off correctly), and this doesn't seem to be the problem. For example, i've just repaired the database and with 30 minutes it's corrupted again. And this is with only 2 people logged on (using the Citrix front end), and they are both still using the database, so it can't be anything to do with closing the database incorrectly.

I've also created a log which records which user has corrupted the database. I just checked and it's reporting that both users are marked as suspect, lol. I guess all evidence points towards the Citrix server, somehow. The only thing i know nothing about! Do u think it would be possible that the citrix client is losing it's connection momentarily, allowing them to keep working, but marking their connection as suspect?

Both the server the db is on and the Citrix server are running Win2000 with service pack 3 installed, so that rules out the opportunistic locking problem doesn't it?