Thank you George. Your suggestions were most welcome as well.

>>Hi all,
>>I have a project for a DLL that holds my business rules. My project has only one program called: BizObj.prg which has an Olepublic class: Security. I have references to stored procedures in a database called: fwdb.dbc inside the BizObj.prg. There is a property in the Security class that will hold the location of the database file. For VFP to compile a DLL, I have to add the fwdb.dbc to the project. So far, everything is fine.
>>
>>My question is, when I deploy the DLL, do I need to include the database files? Or will setting the data location property sufficient to implement the dll assuming that the correct database will be assigned.
>>
>>I am not trying to make a generic dll. I am just separating the tiers.
>
>Ramil,
>
>You'll have to deploy the database as well unless it is available on another computer that the DLL has access to.
>
>Two suggestions in this area:
>
>1. If the DLL is a local COM or if it's a COM+ server, using relative pathing, or better, no pathing (keep it in the same directory) to refer to the database and make sure your installation installs there.
>
>2. Don't use drive specifiers if the server resides on the network. Use UNC's instead.