I have never used this feature before either, so I just opened up the scripts to look at it. When I open up the individual scripts, it behaves just as you say - it wants to create a file called yyy_Clone Clone.102. But if I just click the button on the admin screen, it behaves as I would expect - it creates a properly named clone for each file in the directory Clones, which is located within the ebase directory. I would say that something on your copy is different from "as shipped" but I don't know what it is. Do you have a directory called Clones within the ebase directory? Not sure that would cause the problem you observed, either. I just tried that, and ebase happily created clones into the main ebase directory. >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 >--------------------------------------------------------------------- -- Dave Shaw Northwest Classics, Inc tel: 206-954-7526 fax: 206-625-1338 ------------------ 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 ---------------------------------------------------------------------
