I am having problems with cloning. I have never tried it before. I know how
to fix it but I don't understand. For example when I say clone on the admin2
screen I get the following message for each file:

yyy_Clone.102 could not be created on this disk. Use a different name, make
more room on the disk,remove write-protection or use a different disk. [all
blatant lies]

If I go into each save clone script and and look at what file it wants to
write, it says yyy_Clone Clone.102. If I change that to yyy_Clone.102, do a
save and then perform the script it works and doing a clone from the admin
screen works. If I look at the script again it again wants to put the clone
in yyy_Clone Clone.102. Cancelling leaves it working. I suspect that it has
saved (somewhere hidden) the fact that when the files were shipped it was
assumed that they would reside in wherever the default directory is. They
don't, either on my home machine or certainly not in at work where they
reside where FM Server wants to put them. Of course I can't fix the one in
ebase.102.

I am pretty sure this is broken as designed, i.e. a FileMaker bug

It would be a nice change (for V2) to fix this and put the files in a clone
subdirectory of wherever the files reside. For server this will mean that
the clones are not opened automatically by the server since it only opens
files in the server directory or one level (not two) down from it. It would
be even better if they were saved with an extension of .clone, i.e.
yyy_.clone instead of yyy_clone.102 because of FileMaker's bug of opening
files anywhere on the disk when it choses to be obnoxious.


------------------ 
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support  and enter the email address 
you used to subscribe to the ebase support list:: [email protected]

To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
 ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------

Reply via email to