Hi
For server you need an static IP address or you can use its name/URL.
For client you need ODBC driver and client DLL.

Normally, you only have to specify server host IP address or URL in connection parameters to be able to connect (... DBNAME=www.myserver.com:mydbalias; ...)

You can programatically create DSN entry on client workstations, (better with blank user name and password). There is a DSN class in download section.

Also you can build and set connection string in DBC with DBSETPROP(). But if the connection string contain user name and password, this is again not secure.

I work on a project where the database must be accessible by remote offices over a DSL connection.

I've installed ZeBeDee utility (can act both as a server and client ) and this compress and encrypts traffic between clients and server. The default port used by Firebird can be blocked by firewall.
Usage of private keys is possible, or defining an IP addresses list used to allow connections.

But the most obvious advantage is compression. The traffic is compressed 5 to 9 times.



>Hi all,
>
>I have this small app working in VFP6 using FireBird as the backend. I have successfully tested this app on my machine. Now I want to make this app work as if the data is on the internet and the app is on a client machine. I have a local LAN at the disposal, if it helps.
>
>What I want to do is know the feel of the configurations needed on both the server and client machines, that I will require in a real-life app.
>
>Any suggestions.