Clif, Thanks for the information.
My probelem was a simple oversight. I have developed some additional relational file with ebase and one of these files was on my workstation but not on the server. Since, I am not ready to use this file on the server yet, I just deleted the relationship and voila everyone can delete now. Donna E. Trost Development Coordinator YES! Magazine/Positive Futures Network PO Box 10818 Bainbridge Island, WA 98110 telephone: (206) 842-5009 ext 224 subscriptions: (800) 937-4451 fax: (206) 842-5208 email: [EMAIL PROTECTED] web: www.yesmagazine.org [EMAIL PROTECTED] writes: >Subject: FW: Deleting Records on a server >From: "Clif Graves" <[EMAIL PROTECTED]> >Date: Thu, 14 Mar 2002 18:21:00 -0500 >X-Message-Number: 4 > >Donna, Looks like my original response got lost here it is forwarded from >my >send bin. >Clif >> -----Original Message----- >> From: Clif Graves [mailto:[EMAIL PROTECTED]] >> Sent: Thursday, March 14, 2002 9:17 AM >> To: TechRocks Support >> Subject: RE: [support] Deleting Records on a server >> >> >> From what you said, something is very wrong. In an unmodified >> ebase 1.x on a filemaker network environment the only limit to >> deleting records should be that you can't delete a record which >> another user is currently in. ------------------ 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 ---------------------------------------------------------------------
