Software

Ask something
Discussion Locked

Blinking cursor in Access 2K on TS W2k

0 helpful
3 replies

by manuela 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When you connect via thin client to an Access 2000 database running on a W2K terminal server, when you move the cursor to any empty field, the cursor blinks for a long time before allowing you to input text. Moving to the same fields with the keyboard tab does not present this problem but it is very laborious as different users will fill in different fields. This behaviour is reproduced by using MS Northwind sample database as well, i.e. it is not just our db. I have not been able to find anything on the support sites. Is there a registry key I can change or any other suggestion to troubleshoot this problem. I have also checked with other people and this seems a general Access on Terminal server problem without a solution. Would appreciateany idea as I am at loggerheads.

3 replies

by jillbean

One thing I can tell you is that this is NOT a general access2000 on w2k ts problem. There are some that have to do with queries - but it doesn't sound like that. And I got five different terminal servers at different sites running access2000 to prove it.

Small suggestions:
Turn off track autocorrect on names
Turn off show animations
Turn off personalized menus in access
Turn off menu animations

Larger suggestions:

What you are describing is more characteristic of Citrix and ica. If you have citrix, can you try running same tasks on rdp instead(and do use the downloadable client for XP terminal services if you are at an actual computer - its really nice and will work with any terminal server)? If problem goes away, then look at upgrading to Metaframe XP - has many latency improvements. If you are already running rdp on a computer - try the new xp client anyway.

Service Pack 1 & 2 for Office2k? (chgusr /install - do service pack - chgusr /execute) Some patches there for Access on TS!

Is server overburdened? Access is a ram whale. Multiple Access users are a school of whales. School of whales in a bathtub produces unpredictable results.

Get a more modern transform and re-install (don't think it willdo anything for you, but the early transforms didn't work right). Less labor intensive - repair your installation and then reapply service packs.

If it is a single file database - both forms and tables are in the same mdb file then SPLIT IT.
Each user should have their OWN copy of the mdb with the forms and queries in it.

This discussion is closed to new replies.