Windows Server 2008 R2, new installation, plenty of RAM etc., few users, only roles installed is Remote Desktop Services (and IIS).
An ACCESS 2007 Frontend connects with ODBC native 10.0 driver and ADO to Backend on dedicated SQL 2008 server, plenty Ram etc.
The Access application runs smoothly on stand-alone Client PC's (Win7/XP).
The Access application runs smoothly on SOME of the RemoteDesktop (RD) clients,
and the weird thing is: On most of the others RD-users the application hangs,m with event id 1002.
In addition(?) I did experience that if Access has setting to use "OVERLAPPING" windows, then Access will not close on the RD (still smoothly running on the PC's),
but if I use "TABBED" windows then it closes fine. This is to live with - but also weird.
But it stopping all work that the RD's is hanging.
The two users that I got to work is firstly the "admin"-permissions user, that I used as "master" for testing, and it just worked fine (when set to that TABBED windows...).
The second user that works was first not working (hanging...) but after several tries, and last a debugging (where I did not find any hanging moments) - then it suddenly worked. Nice :-) But even more doissapoiting, that the next user has same problem = hanging cosistenly.
Any ideas? I DID try: no antivirus, and swetting MaxBufferSize to maximum (from 0), and combination of these ideas from googling...
I gave full permissions. I can start in debug mpode (shift down) and do something, but not start the "big" application. Weird...