|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
February 18th, 2009, 09:05 PM
posted to microsoft.public.access.queries
|
|||
|
|||
Access 2003 on Terminal Server 2008
Hi,
I have 15 people Terminal Serving in to our office to enter data into an Access 2003 database, each with their own TS login account. What database configuration will give give me the best performance? Should I split the database? If so should each user have their own front end app? Thanks, Ken 
|
|
#2
February 19th, 2009, 03:11 AM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Access 2003 on Terminal Server 2008
On Wed, 18 Feb 2009 13:05:03 -0800, KPR
wrote: All documentation I have ever seen about this topic SCREAM the same recommendation: every user must have their own FE. If you don't like the performance, work at that following the standard recommendations for split databases, but don't go back to a monolithic db. -Tom. Microsoft Access MVP Hi, I have 15 people Terminal Serving in to our office to enter data into an Access 2003 database, each with their own TS login account. What database configuration will give give me the best performance? Should I split the database? If so should each user have their own front end app? Thanks, Ken
|
|
#3
February 19th, 2009, 08:04 PM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Access 2003 on Terminal Server 2008
Thanks Tom, what are the stadard recommendations for split databases?
"Tom van Stiphout" wrote: On Wed, 18 Feb 2009 13:05:03 -0800, KPR wrote: All documentation I have ever seen about this topic SCREAM the same recommendation: every user must have their own FE. If you don't like the performance, work at that following the standard recommendations for split databases, but don't go back to a monolithic db. -Tom. Microsoft Access MVP Hi, I have 15 people Terminal Serving in to our office to enter data into an Access 2003 database, each with their own TS login account. What database configuration will give give me the best performance? Should I split the database? If so should each user have their own front end app? Thanks, Ken
|
|
#4
February 20th, 2009, 04:38 AM
posted to microsoft.public.access.queries
|
|||
|
|||
|
Access 2003 on Terminal Server 2008
On Thu, 19 Feb 2009 12:04:05 -0800, KPR
wrote: I was thinking of this page: http://www.granite.ab.ca/access/performancefaq.htm -Tom. Microsoft Access MVP Thanks Tom, what are the stadard recommendations for split databases? "Tom van Stiphout" wrote: On Wed, 18 Feb 2009 13:05:03 -0800, KPR wrote: All documentation I have ever seen about this topic SCREAM the same recommendation: every user must have their own FE. If you don't like the performance, work at that following the standard recommendations for split databases, but don't go back to a monolithic db. -Tom. Microsoft Access MVP Hi, I have 15 people Terminal Serving in to our office to enter data into an Access 2003 database, each with their own TS login account. What database configuration will give give me the best performance? Should I split the database? If so should each user have their own front end app? Thanks, Ken
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
