Terminal Server and Microsoft Access

[Guest Lisa Moody]

I have a client who is running :

The server is running MS Windows Server 2003 R2, Standard Edition, SP2

 

The MS Terminal Services licensing is Version 5.2 R2

 

We have a software app that uses SQL Anywhere for the backend and Microsoft

Access for the front end. We use UserDSN ODBC connections on this and on

our other terminal services installations and have not had any issues. With

this client, the data retrieval is behaving oddly, with sporadic data

returns. For example, there is a list of billing amounts and when they

first pull the screen, the whole list will show and then later when they go

to that screen, only some of the data will pull in and then other times,

none of the numbers will show. If they close the app and make a new db

connection then all the numbers show again.

 

Is there something in TS that we should be looking at to know if this is a

memory issue or if the connection to the ODBC is being affected in some way?

We're at a loss about what to check on the configuration because we have

other TS clients and nobody has had this situation. We also have straight

up client/server clients and local hosted clients and haven't seen this.

Any ideas of things to check?

 

Thanks,

 

Lisa

[Guest pheonix1t@gmail.com]

Re: Terminal Server and Microsoft Access

 

HI Lisa,

Access on TS is not good idea - please read previous posts.

I'd suggest converting access to a web (asp.net using microsoft tech)

app.

This eliminates all performance problems and scaling problems due to

access.

 

One thing that does stand out is using a USER DSN instead of SYSTEM

DSN.

Why don't you try using a system DSN for term. server? That may fix

it, but access does come with performance problems.

 

Oskar

 

 

 

Lisa Moody wrote:

> I have a client who is running :

> The server is running MS Windows Server 2003 R2, Standard Edition, SP2

>

> The MS Terminal Services licensing is Version 5.2 R2

>

> We have a software app that uses SQL Anywhere for the backend and Microsoft

> Access for the front end. We use UserDSN ODBC connections on this and on

> our other terminal services installations and have not had any issues. With

> this client, the data retrieval is behaving oddly, with sporadic data

> returns. For example, there is a list of billing amounts and when they

> first pull the screen, the whole list will show and then later when they go

> to that screen, only some of the data will pull in and then other times,

> none of the numbers will show. If they close the app and make a new db

> connection then all the numbers show again.

>

> Is there something in TS that we should be looking at to know if this is a

> memory issue or if the connection to the ODBC is being affected in some way?

> We're at a loss about what to check on the configuration because we have

> other TS clients and nobody has had this situation. We also have straight

> up client/server clients and local hosted clients and haven't seen this.

> Any ideas of things to check?

>

> Thanks,

>

> Lisa

[Guest Frane]

Re: Terminal Server and Microsoft Access

 

I am familiar with access perfomance problems but still I have it

configured on two servers working with no problem. Servers have two dual

core CPU and one user can utilize only 25% of one virtual process (one

core). This scenario is working very good. We are planning to convert

access to asp.net+sql but that is a process that will took us long, it is

planned but it is working with our current infrastructure.

I forget to say that for access client needs only internet connection and

they will conenct to terminal services working with access applications in

real time. With web access there is some delay and lots of users find

terminal services environment usefull for this scenario because it is very

fast ad it runs on very strong server, and end users are geting only

picture over network.

 

 

 

 

--

____________________________________

Frane Borozan

Terminal Services and Citrix Presentation Server user logging

http://www.terminalserviceslog.com

[Guest Lisa Moody]

Re: Terminal Server and Microsoft Access

 

Hi Frane,

 

What do you think could be causing our issue? What should we be looking at?

We are running in runtime mode, which we've learned is a necessity on

terminal services. The SQL database that we used is designed for

synchronizing data and holding everything on a local machine, but we do have

two other terminal services clients that use our product with no issues.

 

Oskar, the problem was happening with a SystemDSN, so we switched to see if

there was some conflict happening. There is no difference, it still happens

with either DSN type.

 

Besides not being an answer about what we should be checking on, there are

specific reasons that the data in our product should not be available via a

web app. We get more customers because it is not web based.

 

Thanks,

 

Lisa

"Frane" <frane.borozan@gmail. remove com> wrote in message

news:mr6kohz6xd03$.tht8vfpy9xg2.dlg@40tude.net...

>I am familiar with access perfomance problems but still I have it

> configured on two servers working with no problem. Servers have two dual

> core CPU and one user can utilize only 25% of one virtual process (one

> core). This scenario is working very good. We are planning to convert

> access to asp.net+sql but that is a process that will took us long, it is

> planned but it is working with our current infrastructure.

> I forget to say that for access client needs only internet connection and

> they will conenct to terminal services working with access applications in

> real time. With web access there is some delay and lots of users find

> terminal services environment usefull for this scenario because it is very

> fast ad it runs on very strong server, and end users are geting only

> picture over network.

>

>

>

>

> --

> ____________________________________

> Frane Borozan

> Terminal Services and Citrix Presentation Server user logging

> http://www.terminalserviceslog.com