Terminal server and Access :: performance issues

[jason]

Will I be asking for trouble in assuming that office personnel in another
branch who attempt to add, modify and delete records in an access database
via Terminal Server connection will have no real performance hit.

At the moment, we share excel files over the local server and there seems to
be no problem. I am now attempting to centralize the data in an Access 2000
database but I'm concerned about performance issues....

Should I worry?

- Jason

 

[jason]

Thanks - but do I need to add 'users' to the database or can I let the the
internal database fly without having to do this prior to splitting the
bugger....?

Thanks
Jason

 

[Albert D. Kallal]

The issue of adding users is a separate issue.

My only real point here is that if you do use terminal server, that does NOT
mean you get off the hook of running a split mdb arrangement. Each new Ts
user logging on to the system should get their own session and THEIR OWN
COPY of the front end.

The fact of TS, or simply using a file share in a office network still means
you SHOULD run a split arrangement. You don't have to, but it just goes
against any type of good professional use of ms-access.

http://www.granite.ab.ca/access/splitapp.htm

http://www.microsoft.com/accessdev/articles/bapp97/chapters/ba15_3.htm

 

[jason]

Many thanks for links!

 

[jason]

Albert, just one other thing: Is there a particular point in time one should
do the split....

By this I mean, suppose I am 90% complete on the database and queries and
forms but I know in a few weeks I will need to make changes to first the
forms and then later the underlying tables or queries.

Can I do the split up front and benefit from the FE and BE divide or should
this ONLY be done once you are 100% ready for deployment...?

- Thanks
Jason

 

[Albert D. Kallal]

Ah, yes, when to split? That is interesting question.

My answer is kind of strange:

You will know when to split!

it is true, as you reach towards near completion, and the table changes
start to stabilize, then that about the right time.

Of course, the real drawback of splitting is that making table changes is
something that becomes HARDER when split. So, it is true, you will tend to
wait until the last possible time.

So, when you feel the table changes are staring to become quite minimal,
that is a good time. No hard and fast rule, but you will kind of just know!