Hi All,
I am really stuck in the middle with this one and am starting to wonder where to turn.
We just dropped $18K on a new terminal server to run our database at work.
This new server is using the windows server 2010 operating system and is using 32bit Access 2010 runtime talking to three Access BE tables. We plan to move to SQL but thats another thread for the future.
We have six users connected to seperate front end files on this new server via remote desktop.
The data link is: Server - 100mb switch - fibre cable - 100mb switch - PC's but all the processing and programs are on the server so all we are bringing down the line really is remote screen shots.
In several of our more complex forms that run filters to return large record sets or run update queries to update lots of records to tables we are getting the screen turning white or flicking back to the hidden main menu after about 5-10 seconds of the query being calculated.
We NEVER had this issue on our old server running XP, runtime 2010 via remote desktop, or via the users with runtime on the pcs, with different OS's talking to the BE on the server.
I am really stuck in the middle here. The database designer is saying that its not a database issue, as these things only started happening when we switched servers, which is true. My IT guys says that everything is installed correctly and there is nothing more they can do.
The end result is lots of frustrated users and no real plan how to fix this.
We have tried:
1. Running windows server 2008R2 on the new server - same issue
2. Disabling the firewall - same issue
3. Running direct on the server - same issue
4. turned off all the code in the DB that related to screen painting issues - no better.
Can anyone suggest some other things to try, we are at a real loss here what to do next?
Thanks
JohnG
I am really stuck in the middle with this one and am starting to wonder where to turn.
We just dropped $18K on a new terminal server to run our database at work.
This new server is using the windows server 2010 operating system and is using 32bit Access 2010 runtime talking to three Access BE tables. We plan to move to SQL but thats another thread for the future.
We have six users connected to seperate front end files on this new server via remote desktop.
The data link is: Server - 100mb switch - fibre cable - 100mb switch - PC's but all the processing and programs are on the server so all we are bringing down the line really is remote screen shots.
In several of our more complex forms that run filters to return large record sets or run update queries to update lots of records to tables we are getting the screen turning white or flicking back to the hidden main menu after about 5-10 seconds of the query being calculated.
We NEVER had this issue on our old server running XP, runtime 2010 via remote desktop, or via the users with runtime on the pcs, with different OS's talking to the BE on the server.
I am really stuck in the middle here. The database designer is saying that its not a database issue, as these things only started happening when we switched servers, which is true. My IT guys says that everything is installed correctly and there is nothing more they can do.
The end result is lots of frustrated users and no real plan how to fix this.
We have tried:
1. Running windows server 2008R2 on the new server - same issue
2. Disabling the firewall - same issue
3. Running direct on the server - same issue
4. turned off all the code in the DB that related to screen painting issues - no better.
Can anyone suggest some other things to try, we are at a real loss here what to do next?
Thanks
JohnG