hello,
we have users connecting to a windows 2000 terminal server from mostly winxp
pro workstations, and for some reason the user can do normal functions in our
database built w/ access 2000. after a few minutes.. 5-10 minutes data is no
longer available. For example pulling up a report in print preivew will say
"there is no data to print".
Im not sure what's causing this, does anybody have any insights?
thanks
seth - 05 May 2006 01:21 GMT
does this happen only in a terminal session, or does it occur locally as
well?
if it happens locally also, i would post that question to the access group
as it probably isn't a terminal server issue
> hello,
>
[quoted text clipped - 11 lines]
>
> thanks