Steve Capistrant
scapistrant at symphonyinfo.com
Thu Jun 19 09:24:17 CDT 2003
A lower tech option: Make sure you have a mapped drive to your network with the central database. Let's say it is drive "Z". Should be a consistent mapping letter for all users. Then in your startup form, perform a test to see if you can open a file (any file) in the target folder. If it generates an error, you can assume that you are not on the network. Either way, you write code to handle the situation (on or off network). <code> 'Verify: File must exist strFullPath = "Z:\xxx\xxx" If Dir(strFullPath) = "" Then MsgBox "You are not connected to the network.", vbOKOnly, "Networking Status" 'Code here to work with remote copy of data else MsgBox "You are connected to the network.", vbOKOnly, "Networking Status" 'Code here to remind user to synchronize if they haven't already End If <end code> Steve Capistrant Symphony Information Services scapistrant at symphonyinfo.com Phone: 612-333-1311 www.symphonyinfo.com 212 3rd Ave N, Ste 404 Minneapolis, MN 55401 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Jim DeMarco Sent: Thursday, June 19, 2003 9:01 AM To: accessd at databaseadvisors.com Subject: RE: [AccessD] detect network Bruce, I'm not familiar with network APIs. Can you point me to any reference material? Someone suggested pinging the server but I'm not sure how to do that in VB/VBA. Thanks, Jim DeMarco