>Walt: I may have expressed my problem incorrectly. I don't believe it's the >import file that is corrupted at this point, but the import "script". When I >select the admin button named "Import a File into Names Table", the error >message i get reads: "the script cannot be found or is deleted." Can I fix >the import script? I tried to import a virgin databse file and the message >was the same.
FileMaker scripts are embedded in the file structure, so Walt's right, the file is damaged. Further, several scripts are called during the import process in at least three different files, import1_102, import0_.102, and names_.102. The chance of locating the damaged script and replacing it without causing downstream trouble is vanishingly small. Best course is to toss the import files and replace them with new files, as Walt suggests. You say you "imported" a virgin database file. Does that mean delete the damaged one and replacing it, or importing data from a new one. The file needs to be replaced. If replacing the import files doesn't fix the problem, the damage is in the names file and you should revert to your best backup. -- -- Dave Shaw H4 Consulting 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 ---------------------------------------------------------------------
