Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ronanpcs
Starting Member
6 Posts |
 Posted - 2007-04-16 : 10:14:31
|
| This is puzzling.........We have an application running on our new Windows 2003 Server terminal server that accesses a SQL database from our file server. The ODBC is set up properly (based on how is was set up on the old Windows 2000 terminal server) and everything appears to be the same. However, when we load the application and attempt to bring up client data, the data doesn't appear in the screens, but it's there. We can dbl-click in the window where the data should be displaying and have the subsequent window appear (with no visible data). We know the data is there because one of the sub-windows displays the client's name in a static header. We've tried to run the app in Windows 2000 compatibility mode, but no change.Has anyone ever run across this? Any help would be appreciated.ronanpcs |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-04-16 : 10:51:17
|
| My guess is that this is a problem with the application, not a database issue.CODO ERGO SUM |
 |
|
|
|
|
|
Data not visible