>Thanks for the quick response. I have downloaded the driver and run the setup program. It puts a "DBISAMOD.DLL" file in a unique path. Do I need to copy this file into my VFP directory?

If you've installed it on your machine Windows will take care of the DLL from there. You will need to install it on each client machine and there will be a way to do this in your setup program. When you get to this part you can come back with more questions.

>And as you have guessed, I am at a loss of what to do next.

Go to your "Data Sources (ODBC)" dialog - mine's in the Control Panel. Click "Add" to make a new data source. The first thing it asks you is for the name of the driver - choose the DBISAM driver. The next dialog that comes up depends on the driver so I don't know what yours will say, but somewhere in there you will need to give it a name and for now we'll call it "MyDBISAM." You may also need to give the IP of the server or the local or network directory where the data is located.

>I want to access the DBISAM file and pull the name, rate, paycycle and period and store the infomation in memory variables for use in my app.

In your DBC you should make a connection (in the Project Manager select Connections and click New) to your datasource. Choose "Data source, userid, password," and in the Data source box put the name you gave your data source (MyDBISAM). Fill in whatever you have for UserID and PW and the rest of the defaults are OK for now. Your connection needs a name so we'll call it "MyConnectionToMyDBISAM." (I'm sure you'll want something shorter < g >.)

When you need to get data from your DBISAM data source you can use either a remote view or SQL Pass-through. These are described in the Client Server sections of the Help which comes with VFP. It's pretty much the same no matter what the back end data source is and that's the beauty of client server databases.

After you've read the Help and tried out either a Remote View or SQL Pass-through come back with more specific questions about what didn't work.

By the way, you can also do all of this stuff with MS Access, for example. (If you have Access you'll notice an ODBC driver for it in the list.) It's nice to have someting easy and familiar to work with when you're learning the ropes with Client-Server databases.