AccessDiscussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
I have been asked to deploy an access database onto our win2003 server in which clients will connect via a terminal service connection. These connections will be of a remote basis so i have split the database (B/End and F/End). The database was designed for a multi-user enviroment and has tested in a local network with no problems. My questions are has anyone else attempted running an access database in a terminal service enviroment and if so are there any known problems and also, win2003 server stores a client connection ID when a term service connection is made is there some VBA code that anyone knows to enable me to capture and store that ID when a user logs into the database?
I am not sure why you would run a front end FROM a terminal service session. If the workstation can see the server to run the session, it can see the server to run an access front end from the local PC or from a network share to a back end on a file server. You certainly wouldn't run a back end from anything but a front end, so I don't think you are saying you would run a back end from a session. What is it you are trying to do?