 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 1 / March 2008Remote Desktop Connection
Hi guys I have a Frontend and Backend DB that works well on my LAN. I use a INI file Path, to access a mapped network connection back to the Backend Data file. [DBInfo] Path=F:\Server\Data.mdb I have a situation now that requires a Remote Connection with my Program. A remote client is using a notebook (XP Pro) with a Wireless Broadband, with the frontend running on his notebook. The Server is MS Server 2003 with Terminal Services. I need help with these issues! 1/ To setup a Remote Mapped Network Connection from the Remote Notebook (using Remote Desktop Connection) to the Server (using Terminal Services) Backend Data File. 2/ To Edit the INI File so the Frontend finds the Backend when the Remote User opens the Frontend. Any help on these matters will be greatly appreciated! Thanks for your time and effort!!!! Chris Not so fast. You are confusing a few concepts. You cannot use RDC to create a connection to SQL Server. This has to do with different ports and protocols. (assuming the server is accessible only over the Internet, not a LAN) Rather, the server has to expose the SQL Server to the Internet, of course properly secured, and the firewall has to open port 1433 (by default). Then you can build a connectionstring to that SQL Server using the info here: www.connectionstrings.com INI files (an outdated concept) are edited using GetPrivateProfileString API and its cousins. -Tom. >Hi guys > [quoted text clipped - 27 lines] > >Chris Hi Tom Thank you for your help! The Server is just a MS Server 2003, not a SQL Server and the data file on the Server is just a mdb Data File (Tables Only). Thanks for the connection site, but that isn't the problem. The issue I need help with is the (Remote Mapped Network Drive) for the Remote Notebook Frontend connection string! Any suggestions with, Terminals Services, VPN, RDC or something else? Thanks again!! Chris So I understand that the back-end is an Access MDB sitting somewhere on a remote server, not on your LAN. You can build a RDC connection to it, but you need to know how to connect your front-end to that back-end. The answer is that you can't in this configuration. Rather you'd want to put your front-end on that server as well, and then connect to it via RDC. That's pretty much indistinguishable from Terminal Services. VPN is not a good solution because connecting to the back-end over a VPN connection which uses the public Internet will experience momentary hiccups of service, and a real potential of database corruption. -Tom. >Hi Tom > [quoted text clipped - 12 lines] > >Chris While I worked at Boeing Aircraft We were told to use UNC paths not mapped paths. Also you can have a relink utility that will process when your app cannot connect to the backend. Let me know if you need one I have one > Hi guys > [quoted text clipped - 27 lines] > > Chris Any of those databases running inside of an aircraft? I'll row to the Netherlands next time I visit the family :-) -Tom. >While I worked at Boeing Aircraft We were told to use UNC paths not mapped >paths. Also you can have a relink utility that will process when your app >cannot connect to the backend. Let me know if you need one I have one <clip> > Any of those databases running inside of an aircraft? > I'll row to the Netherlands next time I visit the family :-) <CHUCKLE> I've had a database running inside an aircraft -- but not very much anymore, as the limited space between rows of seats in coach won't allow me to open my notebook, get at the keyboard, and view the screen. Maybe if there's some unusual happening and I get upgraded to business or first class... Larry Linson |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2012 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.