A very important warning about the Export command

[Robert Ameeti]

A warning to others and a note to our leader.

I do strongly believe in the Hippocratic Oath as 
it pertains to my clients in that I will keep 
them from harm and injustice and to that end, I 
am making this post about a pitfall of the Export 
command.

The below commands were a part of a 
..CloseDatabase procedure. It all worked fine 
until the Share was not available. When the path 
for the text file became unavailable, Panorama 
proceeded to write the data to a text file but 
wrote this information over and on top of the 
Panorama database file that was being closed by 
the user via the Close button. NEVER EVER should 
Panorama write over and replace the existing in 
use database with text data just because the path 
is not available. Yes, a programmer can (and 
should perhaps) first check to see if the path is 
currently available but regardless of whether 
they are smart enough (or experienced enough) to 
do this, the Panorama file should not disappear 
and become a text file. Interesting too that the 
file name does not get changed but instead the 
Panorama file name continues to be used with raw 
text data taking the place of the data, forms, & 
procedures. Fortunately there was a backup of the 
important data.

Export "Public:Export folder:"+"Customers Data.txt", Str(IDNumber)+","+Name+¶
Save
ContinueClose "Yes"

-- 

<><><><><><><><><><><><><><><><><><>
Robert Ameeti

Cooperation can only be reached if we work together.

<><><><><><><><><><><><><><><><><><>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://provue.com/pipermail/qna/attachments/20080304/fb099f88/attachment.html