N
Newbie
Hi,
Scenario:
SQL Server BackEnd
Access FrontEnd loaded on each client PC
I have some reports that rely on records being inserted into local tables
ie. in the FrontEnd - Access. This is because they take far too long to run
by using queries. This works fine when people have access loaded on their
machine and the reports are exported as a snapshot to c:\reports
How can I achieve the same thing when users are using terminal services to
log on to the application? Will each user have to have a copy of the
database in their home directory?
How will the code that looks at the path c:\reports be re-written to take
account of the user that is logged on?
Scenario:
SQL Server BackEnd
Access FrontEnd loaded on each client PC
I have some reports that rely on records being inserted into local tables
ie. in the FrontEnd - Access. This is because they take far too long to run
by using queries. This works fine when people have access loaded on their
machine and the reports are exported as a snapshot to c:\reports
How can I achieve the same thing when users are using terminal services to
log on to the application? Will each user have to have a copy of the
database in their home directory?
How will the code that looks at the path c:\reports be re-written to take
account of the user that is logged on?