Corruption occurring after converting 97->2003 and moving to T.S.

[Gregory K.]

We have an ACC97 application which has been in service for more than 5 yrs.
The app has just been converted to ACC2003, and all users now run on a
Terminal Server.

In less than a week, two records have been damaged (each from a different
table); most of the fields contain garbage, and the record cannot be deleted
(error message "the search key was not found in any record").

In the five yrs of running the app in 97 format we _never_ had this happen
(the worst that ever happened was an occasional damaged memo).

The T.S. is a recent multiprocessor model running Server 2003, all SP's
current.

Any thoughts would be highly appreciated.

 

[Van T. Dinh]

I assume this is a multi-user application since you are using T.S.?

Have you split the database to Front-End and Back-End and set up T.S. so
that each user has his/her own copy of the Front-End on the T.S. server?
This will reduce the likelyhood of corruptions dramatically.

I am using Citrix to run Access2002 accessing SQL Server database. For the
last 12 months, I have had 1 user experiencing the Front-End corruptions
which can easily be fixed by creating a new Front-End for him. No problems
with data in the Back-End to date.

 

[Gregory K.]

- Yes it is multiuser (8 - 12 on a given day)
- App is split b/e f/e
- everyone uses a shared f/e
- the old system (on NT4) had some users with a local copy, the rest (6 - 8
at a time) running on Metaframe 1.8
- the corruption is occurring in the b/e (the data file)
- now 4 incidents - less than a week in service

Thanks & best regards

 

[Van T. Dinh]

Try giving each user a copy of the Front-End, even on MetaFrame.

You can use Tony Toews' AutoFE to automate the update of the Front-End to
each user. See:

http://www.granite.ab.ca/access/autofe.htm