Article View: comp.databases.ms-access
Article #132Re: Access database over VPN
From: Albert D. Kallal
Date: Wed, 18 Dec 2002 17:58
Date: Wed, 18 Dec 2002 17:58
44 lines
3631 bytes
3631 bytes
Any consultant or network support company that suggests to even waste your time attempting to run ms-access as a file share across a wan on a VPN should be fired. Simply put, you will damage and corrupt that file on a regular bases. I am not sure who is the consultant who set up the VPN, but don't these people ask a few basic questions as to the type of software and applications you are running? This is just sheer incompetence, and gives the IT industry a bad name. You cannot even come close to attempting this. Of course you are not going to get enough speed. (did not anyone check the difference in speed between a office LAN and a vpn?). Assuming someone did come along and get you enough speed, as mentioned, a wan is subject to temporality dis connects, and that will damage the ms-access database on a regular bases. (you will have to resort to the previous days backup on a regular bases). You have several solutions. You could modify the application to work with sql-server. However, to make sure that the application uses a absolute minimum of bandwidth, you really need some careful designs. The best solution is to use some thin client technology. Windows Terminal Server is the best solution here. With any connection faster than a 56k modem, your users will not even tell the difference between running it locally, or remotely on the side of the country. TS absolute rocks, and runs circles around products like VNC (which is free), or products like pc-anywhere. If you are running windows 2000 server, then you can test how well the application will run. You get two free TS licensee on windows 2000 server. (just setup TS to be run in adim mode..it is only a few mouse clicks, but does require a server re-boot). In fact, TS is even workable from a modem connection also. You did not say how many remote users you need, but TS is a great way to go, since you do NOT have to re-write one line of code. You can also run your application through the browser if you also start running IIS on the server, but don't think that is needed. -- Albert D. Kallal Edmonton, Alberta Canada kallal@msn.com www.attcanada.net/~kallal.msn
Technical Details
Message-ID:
<4H2M9.186423$ea.3832999@news2.calgary.shaw.ca>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!sjc70.webusenet.com!news.webusenet.com!pd2nf1so.cg.shawcable.net!residential.shaw.ca!news2.calgary.shaw.ca.POSTED!not-for-mailReferences:
<216f24b2.0212180930.13633982@posting.google.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff0ac,909d6cf07e074b0f X-Google-Attributes: gidff0ac,public X-Google-Thread: 109779,909d6cf07e074b0f X-Google-Attributes: gid109779,public X-Google-Thread: 10de66,909d6cf07e074b0f X-Google-Attributes: gid10de66,public X-Google-Thread: 10fd83,909d6cf07e074b0f X-Google-Attributes: gid10fd83,public X-Google-ArrivalTime: 2002-12-18 09:58:26 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!sjc70.webusenet.com!news.webusenet.com!pd2nf1so.cg.shawcable.net!residential.shaw.ca!news2.calgary.shaw.ca.POSTED!not-for-mail X-Trace-PostClient-IP: 24.86.29.142 From: "Albert D. Kallal" <kallal@msn.com> Newsgroups: comp.databases.ms-access,borland.public.delphi.database.sqlservers,mailing.database.mysql-java,mailing.database.mysql References: <216f24b2.0212180930.13633982@posting.google.com> Subject: Re: Access database over VPN Lines: 46 Organization: HCS Consulting Group X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: <4H2M9.186423$ea.3832999@news2.calgary.shaw.ca> Date: Wed, 18 Dec 2002 17:58:24 GMT NNTP-Posting-Host: 24.70.95.207 X-Complaints-To: abuse@shaw.ca X-Trace: news2.calgary.shaw.ca 1040234304 24.70.95.207 (Wed, 18 Dec 2002 10:58:24 MST) NNTP-Posting-Date: Wed, 18 Dec 2002 10:58:24 MST