Access and Citrix

[Rob]

I thought I posted this yesterday, but can't find it. So if this ends
up showing up twice, please forgive me.

I am an Access developer and have done many Access databases in the
standard Front-end on the workstations, backend on the server
(over a LAN) but have never worked with Access over Citrix, though
that situation is coming up for me shortly.

Question: When you run the front-end on the Server, does Citrix clone
the front
end application database file for each user that connects or do they
all connect
to physically the same front-end file?
The real question here is: If user1 adds rows to a table that is
local in the
front-end will user 2 be able to see those records (assuming they have
the
proper table permissions)? If they were running in physically the
exact same
front-end file, they would be able to see each others records. If
Citrix gives
each user their own workspace and a copy of the front-end, they
wouldn't.
Any enlightenment you could provide would be appreciated.
Thanks

[Rick Brandt]

"Rob" <si****@ensco.c om> wrote in message
news:bd******** *************** **@posting.goog le.com...

I thought I posted this yesterday, but can't find it. So if this ends
up showing up twice, please forgive me.

I am an Access developer and have done many Access databases in the
standard Front-end on the workstations, backend on the server
(over a LAN) but have never worked with Access over Citrix, though
that situation is coming up for me shortly.

Question: When you run the front-end on the Server, does Citrix clone
the front
end application database file for each user that connects or do they
all connect
to physically the same front-end file?

Unless you provide a means to give each user their own copy of the front
end on the Citrix server then they will all be opening the same physical
file and you risk the same corruption issues as if you were sharing a
common front end when NOT using Citrix.

If there is a table that all users need to see edits and insertions on then
it doesn't belong in the front end file.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Rob]

I have a question. Who went back and connected all these threads for me?
I appreciate it. Is this a 'manual process?'
Rob

[Tony Toews]

si****@ensco.co m (Rob) wrote:

I have a question. Who went back and connected all these threads for me?
I appreciate it. Is this a 'manual process?'

No one. Ah, you're posting from Google. It can take a few hours or even a day
before a posting appears on Google.

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

[Tony Toews]

si****@ensco.co m (Rob) wrote:

I thought I posted this yesterday, but can't find it. So if this ends
up showing up twice, please forgive me.

And I responded to your previous thread.

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

[XMVP]

"Rick Brandt" <ri*********@ho tmail.com> wrote in message
news:2h******** ****@uni-berlin.de...

Unless you provide a means to give each user their own copy of the front
end on the Citrix server then they will all be opening the same physical
file and you risk the same corruption issues as if you were sharing a
common front end when NOT using Citrix.

1. Multiple front ends defeat the purpose of Citrix.

2. The "shared" table in the front end will not cause corruption. Rather
record conflicts will result.

[Rick Brandt]

"XMVP" <ac***********@ hotmail.com> wrote in message
news:i7******** ************@vn et-inc.com...

"Rick Brandt" <ri*********@ho tmail.com> wrote in message
news:2h******** ****@uni-berlin.de...

Unless you provide a means to give each user their own copy of the front
end on the Citrix server then they will all be opening the same physical
file and you risk the same corruption issues as if you were sharing a
common front end when NOT using Citrix.

1. Multiple front ends defeat the purpose of Citrix.

2. The "shared" table in the front end will not cause corruption. Rather
record conflicts will result.

This statement implies that all problems associated with sharing a front end are
network related. Is that what your saying? That may very well be true, but I
haven't seen anything definitive that states that. Even if true this would only
be the case if the shared front end file was located on the Citrix server's
local drives, no? We have certainly seen cases where Citrix/TS was being used
to run apps located on other servers in which case I see no difference at all
regarding sharing front ends.

There are many benefits to Citrix (Terminal Server) besides making application
distribution simpler. One can use standard "one front end per user" practices
and still realize these other benefits.

In addition (at least in my apps), there are situations with local tables, or
when modifying the SQL in a QueryDef where having more than one user in the same
file would cause "problems" even if not "corruption ".
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

[Tony Toews]

"XMVP" <ac***********@ hotmail.com> wrote:

Unless you provide a means to give each user their own copy of the front
end on the Citrix server then they will all be opening the same physical
file and you risk the same corruption issues as if you were sharing a
common front end when NOT using Citrix.

1. Multiple front ends defeat the purpose of Citrix.

Why? And so what? That solves corruption problems.
2. The "shared" table in the front end will not cause corruption. Rather
record conflicts will result.

Rick never stated the shared table would cause corruptions.

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

[Rob]

Tony Toews <tt****@teluspl anet.net> wrote in message news:<gk******* *************** **********@4ax. com>...

si****@ensco.co m (Rob) wrote:

I thought I posted this yesterday, but can't find it. So if this ends
up showing up twice, please forgive me.

And I responded to your previous thread.

Tony

No, what I meant was. I posted item 6 in this thread from scratch.
Not attached to anything, just posted the original item. The next day
it was attached to items 1 through 5. I assume that the message board
software did it automatically based on my subject line. I guess that I
just supplied "Access and Citrix" which just happened to correspond to
the subject of a previous thread. That how it works?
(By the way I'm (essentially) a newbie at newsgroups because my work
environment is on a "standalone network" of sorts).
Thanks,
Rob

[Rick Brandt]

"Rob" <si****@ensco.c om> wrote in message
news:bd******** *************** **@posting.goog le.com...

Tony Toews <tt****@teluspl anet.net> wrote in message

news:<gk******* *************** **********@4ax. com>...

si****@ensco.co m (Rob) wrote:

I thought I posted this yesterday, but can't find it. So if this ends
up showing up twice, please forgive me.

And I responded to your previous thread.

Tony

No, what I meant was. I posted item 6 in this thread from scratch.
Not attached to anything, just posted the original item. The next day
it was attached to items 1 through 5. I assume that the message board
software did it automatically based on my subject line. I guess that I
just supplied "Access and Citrix" which just happened to correspond to
the subject of a previous thread. That how it works?
(By the way I'm (essentially) a newbie at newsgroups because my work
environment is on a "standalone network" of sorts).
Thanks,
Rob

Google groups thread by subject line which is actually a HORRIBLE way to do
it. If you post a relatively generic subject, it will get grouped with
posts from 10 years ago.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com