I have virtually the same project you do.
Since I had FoxPro as client and data server on a LAN, (I actually tried mapping from remote office - EXTREMELY slow) the natural step, for remote office was:
VFP 8 as front end, SQL Server 2000 as back end. Project is near completion. Feel free to...
Hello.
I have a SQL Server that, say, has an instance name of ibm/mydata.
On a local workstation, I open ODBC and establish a connection easily. Ibm/mydata automatically appears as the path when I'm using the ODBC wizard.
However, take that worstation to a remote location and I cannot see...
Hello!
We have a Main Office with a LAN including a Server, running SQL Server 2000.
The Workstations (on W2k Pro) all connect to SQL Server (using ODBC) successfully.
Now, take one of those workstations and move it to a remote
office (the remote office is connected to the Main Office via...
if a mapped drive works for you (ie: net use f: \\serverIP\sharename) and you're just looking to simplify access for other users, perhaps you can automate the mapping for them.
Ie:
create a batch file that will perform the NET USE function, email to them and have them run it whenever required...
I have recently completed a project of similar configuration...
Branch office connected to Main office.
Branch office had a Netopia router that negotiated VPN with another Netopia router at the Main office.
My configuration on 3Mbps was extremely slow - more than 50% of packets dropped most of...
Hello,
As a new project, I have a branch office connecting to the main office where Visual Foxpro data is located, at the server...
the PCs at the branch office have UNC mappings directly to the data directory at the Server (at Main office).
The connection is extremely slow. Each PC has a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.