Front End Corruption?

[wmddgm]

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?

 

[DonQuichote]

You can probably corrupt databases in many ways. Try working on a database on a CD-rewritable and you know what I mean. There are other ways, through code too. To name a few: try to display a non-existing toolbar from code or feed the Jet engine a java-sql styled parameterquery (like

SELECT * FROM tblWhatever WHERE lngId=?[code]) These are very quick ways to exit MS-Access!

[i]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?[/i]

That probably makes no difference whatsoever to the problem you encountered. It sounds like citrix is your problem here. I don't even know what kind of program that is, but I would start to look there.

Best regards

 

[mkov]

I have quite a few users using a database over Citrix, and have never had a problem. They are sharing a frontend that is linked to 3 backend databases. What version of Access are you using? I am using 2000. You may want to try having the Citrix users upgrade to the most current version, doubt that will help, but it is worth a try. You could also reinstall Access on the Citrix server, not sure if that will help either though.

DonQuichote,

Citirx is a VPN client.

 

[wmddgm]

Everyone is using Access 2000, and the network servers are running Windows 2000 with service pack 3 installed.

Nobody is closing the database incorrectly, and nearly all the time the person/people involved in corrupting the database continue to work away unaware that it's even corrupt! It's only when someone else tries to log in that they discover it needs repairing.

I've just repaired it and within 30 minutes it's now corrupt again, and that's only with 2 people logged on (both are still using it). I guess it's nothing to do with code, as it's always the Citrix users that are corrupting it.

I just don't know what else it could be?

 

[WalkieTalkie]

Hi there
Did you ever solve this problem? We are having very similar (almost identical, in fact) problems with an Access 97 database where the users were recently moved to the Citrix environment. Currently we're going down the path of upgrading the back end to SQL server, front end to XP, and looking at giving all users their own copy of the front end. But from what I've been reding, not sure that will solve the problem. I'm told by the IT people that its not the Opportunistic Locking issue either.
Any help or advice much appreciated

 

[Hap007]

Hi Guys,

There can be many reasons why the Access FE gets corrupt.
Trying to solve that problem might take years.

So, here is a solution to just eliminate the problem.

1) Get a good copy of the frontend and place it on the server. Call it App-original.mdb (No one should ever run this copy)
2) Modify the logon script or the startup shortcut to fire off a procedure to copy and rename App-Original.mdb to App-Username.mdb and run this App-Username.mdb
3) When the user exits from the app or signs off, delete the copy called App-Username.mdb

By doing this, everyone will run there own copy and the copy it self will not be corrupt from a prior user.

Simple, but it should solve your problem.

Hope This Helps,
Hap


Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Add-on Solutions
Access Consultants forum

http://www.tek-tips.com/threadminder.cfm?pid=1121