Bhav,

>Hi Agnes
>
>>3. Use the VSS integration VFP shiped with VFP. Simply add the DBC to a project that is under VSS and add the it to vss. If you need to work with the DBC you need to check out, but VFP will take care to handle all (DBC/dct/dcx) files.
>
>I am using Perforce actually and it is integrated in VFP project manager just like VSS and uses VSS API. Yes, I was thinking to utilize the integration, but my observation with other binary files like vcx/t/a, as soon as the classlib is checked in it is marked as readonly, I guess the same will happen for DBC/t/x, then won't my app complain when I run it that it can't write to the dbc?
>
>What do you do, you check the dbc out everytime before using the app and then check in later (with all the new sample data that you might have put in)? I mean what is the ideal method, VSSing the sample data is something I am not able to digest.
>
>What happens to the dbf where the actual structures are changed?

Ah. Now it comes.
Yes this is a problem.
Your app should either go in readonly mode or stop acces because of readonly files.

If have no trouble with readonly data since my app is not bound to a single DBC. I create DBC's on the fly.

The DBF/DBC I store in VSS is just metadata and classfactory. My app only needs the one to create the lifetime DBC's and the other describes classes and the like. Since that operations are read only (for the app) no harm is done.

If I like to alter those data, I need tho check out anyway.


>
>Sorry about such newbie questions but I had tried to SC the DBC but had bad experience of readonly problem and believed that was never meant to be.

Never mind.

AFK
Agnes