MS Access on Terminal Server.

[Henry Craven]

Hi Everyone..
Been forever since I've posted to the Access newsgroups, and even longer
since I've needed to post a question, but I've never had to use or try
Access on a Terminal Server so I'm hoping to Brain Scrape some info from
those of you that have.

Schema:
MS Access 2000 .adp sitting on a Terminal Server with SQL Server
Database backend.

Issue:
Need to have User specific Temporary Tables.

Assumptions:
As the logged-on TS User is presented with an instance of Access, this
Instance is user specific, so any temporary tables created in the
"Front-end" would be specific to that user.

On ending the TS Session the MS Access instance is destroyed and any
temporary tables with it so no clean-up / table destruct is required on
closing the App.

Question:
Are the above assumptions correct ?

Supplemental Question.
Other than using Temp Tables so an additional Field (value holder) can
be added ( SQL Database cannot be altered ) is there any -other- way to
conditionally format selected records in a continuous form that anyone
has devised/discovered ?

TIA

Henry Craven.

[Tom van Stiphout]

On Sun, 18 Jul 2004 23:55:38 GMT, "Henry Craven" <IU******@Dot.Nyet>
wrote:

Hi Henry,

Good to have you back.
ADP doesn't have tables in the front-end, only in the back-end.
However, since the back-end is SQL Server, you can certainly have
temporary tables there. Their names start with # or ##. See BOL for
details. An alternative I've used several times is to have a permanent
table, with an extra MachineName column, used to separate the
temporary data from the several users.

You give TS too much credit. It's a pretty stupid window into the
server. If you set up each user with her own home folder, and her own
copy of the front-end (after all, disk space is cheap), then each user
would be using a personal version of the FE.

Of course if you BADLY wanted local tables, you could always use
Automation to connect to an MDB (one for each user in their own home
folder).

Regards,

-Tom.

Hi Everyone..
Been forever since I've posted to the Access newsgroups, and even longer
since I've needed to post a question, but I've never had to use or try
Access on a Terminal Server so I'm hoping to Brain Scrape some info from
those of you that have.

Schema:
MS Access 2000 .adp sitting on a Terminal Server with SQL Server
Database backend.

Issue:
Need to have User specific Temporary Tables.

Assumptions:
As the logged-on TS User is presented with an instance of Access, this
Instance is user specific, so any temporary tables created in the
"Front-end" would be specific to that user.

On ending the TS Session the MS Access instance is destroyed and any
temporary tables with it so no clean-up / table destruct is required on
closing the App.

Question:
Are the above assumptions correct ?

Supplemental Question.
Other than using Temp Tables so an additional Field (value holder) can
be added ( SQL Database cannot be altered ) is there any -other- way to
conditionally format selected records in a continuous form that anyone
has devised/discovered ?

TIA

Henry Craven.

[Tony Toews]

Tom van Stiphout <no*************@cox.net> wrote:

An alternative I've used several times is to have a permanent
table, with an extra MachineName column, used to separate the
temporary data from the several users.

Which will be difficult given that the MachineName will be the same for everyone on
the same TS system. You could try userid except that there might be a generic user
such as say Counter or Warehouse, (a concept I disagree with but I digress) or the
user might want to run the app twice.

Now if there was an API for a unique TS task id or something like that.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

[Tom van Stiphout]

On Mon, 19 Jul 2004 05:11:52 GMT, Tony Toews <tt****@telusplanet.net>
wrote:
Good point.
How about @@SPID?
I haven't tried this. but it seems promising.

-Tom.

Tom van Stiphout <no*************@cox.net> wrote:

An alternative I've used several times is to have a permanent
table, with an extra MachineName column, used to separate the
temporary data from the several users.

Which will be difficult given that the MachineName will be the same for everyone on
the same TS system. You could try userid except that there might be a generic user
such as say Counter or Warehouse, (a concept I disagree with but I digress) or the
user might want to run the app twice.

Now if there was an API for a unique TS task id or something like that.

Tony

[Dimitri Furman]

On Jul 19 2004, 01:22 am, Tom van Stiphout <no*************@cox.net> wrote
in news:ve********************************@4ax.com:

How about @@SPID?
I haven't tried this. but it seems promising.

Only if you can ensure that each instance of the app opens only one
connection to the server in its lifetime.

I would probably suggest SUSER_SNAME() function, possibly even using it as
the default for a column in the temp table. This requires every user to
use a unique SQL Server login.

--
remove a 9 to reply by email

[Henry Craven]

Thanks Guys.

I've only ever had a brief look at .adps and I've inherited this mess.
Not the way I'd write this at all, and they haven't left me much room
to manoeuvre in ( eg. I can't alter the SQL Database.)

--
Henry Craven

"Tom van Stiphout" <no*************@cox.net> wrote in message
news:ve********************************@4ax.com...

On Mon, 19 Jul 2004 05:11:52 GMT, Tony Toews <tt****@telusplanet.net>
wrote:
Good point.
How about @@SPID?
I haven't tried this. but it seems promising.

-Tom.

Tom van Stiphout <no*************@cox.net> wrote:

An alternative I've used several times is to have a permanent
table, with an extra MachineName column, used to separate the
temporary data from the several users.

Which will be difficult given that the MachineName will be the same for everyone onthe same TS system. You could try userid except that there might be a generic usersuch as say Counter or Warehouse, (a concept I disagree with but I digress) or theuser might want to run the app twice.

Now if there was an API for a unique TS task id or something like that.
Tony

[Van T. Dinh]

Henry

I guess you are referring to the (SQLServer) "local" temporary Table (with 1
# in from of the Table name - MSKB article 287728) then you assumption is
correct, AFAIK according to B.O.L.

Not sure of the 2nd question as I hardly use ADPs besides a few for testing.

--
HTH
Van T. Dinh
MVP (Access)


"Henry Craven" <IU******@Dot.Nyet> wrote in message
news:_5*****************@news-server.bigpond.net.au...

Hi Everyone..
Been forever since I've posted to the Access newsgroups, and even longer
since I've needed to post a question, but I've never had to use or try
Access on a Terminal Server so I'm hoping to Brain Scrape some info from
those of you that have.

Schema:
MS Access 2000 .adp sitting on a Terminal Server with SQL Server
Database backend.

Issue:
Need to have User specific Temporary Tables.

Assumptions:
As the logged-on TS User is presented with an instance of Access, this
Instance is user specific, so any temporary tables created in the
"Front-end" would be specific to that user.

On ending the TS Session the MS Access instance is destroyed and any
temporary tables with it so no clean-up / table destruct is required on
closing the App.

Question:
Are the above assumptions correct ?

Supplemental Question.
Other than using Temp Tables so an additional Field (value holder) can
be added ( SQL Database cannot be altered ) is there any -other- way to
conditionally format selected records in a continuous form that anyone
has devised/discovered ?

TIA

Henry Craven.

[John Winterbottom]

"Tom van Stiphout" <no*************@cox.net> wrote in message
news:ve********************************@4ax.com...

On Mon, 19 Jul 2004 05:11:52 GMT, Tony Toews <tt****@telusplanet.net>
wrote:
Good point.
How about @@SPID?
I haven't tried this. but it seems promising.

use the SPID of the CurrentProject.Connection object. This will be

a) unique to each running instance of the Access ADP
b) unchanging from the time the app launches to the time it closes

[Dimitri Furman]

On Jul 20 2004, 12:55 pm, "John Winterbottom" <as******@hotmail.com> wrote
in news:2m************@uni-berlin.de:

"Tom van Stiphout" <no*************@cox.net> wrote in message
news:ve********************************@4ax.com...

On Mon, 19 Jul 2004 05:11:52 GMT, Tony Toews <tt****@telusplanet.net>
wrote: Good point.
How about @@SPID?
I haven't tried this. but it seems promising.

use the SPID of the CurrentProject.Connection object. This will be

a) unique to each running instance of the Access ADP
b) unchanging from the time the app launches to the time it closes

John,

I am not too familiar with ADPs, but if the connection gets reset for some
external reason (bad network connectivity, etc.), is it not possible that
the ADP will reconnect while the app is still running, and get a different
SPID?

--
remove a 9 to reply by email