Hi Walter
Forgive me for being dense, but I still don't understand how you get long field names with the COPY TO command (since one is copying to free tables, no?). I have never been successful doing this. Am I missing something?
TIA
Charles
>Hi charles,
>
>>I guess I failed to understand that your approach involved locking all the tables during the duration of the backup.
>
>This will prevent other users to update tables during the process of making copies of the files.
>
>>I was also under the impression that the COPY TO approach lost long field names, so the tables created in the backup would have the possibility of duplicate field names if uniqueness was not established in the first ten characters. Does the copyfile() api call address this problem?
>
>Yes, in fact you're making an exact duplicate of your database files.
>
>>I had just always taken as a matter of faith that DBFs were not appropriate for applications which required 24/7 backup capability.
>
>When designing you application carefully it should be possible. I'll hope this thread will produce a fail-safe strategy.
>
>Walter,
Charles Hankey
Though a good deal is too strange to be believed, nothing is too strange to have happened.
- Thomas Hardy
Half the harm that is done in this world is due to people who want to feel important. They don't mean to do harm-- but the harm does not interest them. Or they do not see it, or they justify it because they are absorbed in the endless struggle to think well of themselves.
-- T. S. Eliot
Democracy is two wolves and a sheep voting on what to have for lunch.
Liberty is a well-armed sheep contesting the vote.
- Ben Franklin
Pardon him, Theodotus. He is a barbarian, and thinks that the customs of his tribe and island are the laws of nature.
