Carl, It seems to me that, since FMP3 and FMP4 use the same file format, that it could be dangerous for both to be available. Since, as Dave has already confirmed, there is more functionality available in v4, I can think of no reason to retain v3 on any computers (other than v3 Server, if it's used). Seems like removing all the v3 copies should clear things up and prevent future problems.
Gary > Subject: Access priviledge problem > From: Carl Paulsen <[EMAIL PROTECTED]> > Date: Fri, 22 Mar 2002 16:13:09 -0500 > X-Message-Number: 4 > > I'm working with a group whose database isn't letting them access > administrative functions. The problem is that the script (514a and b) > which check to confirm what password the user is logged on under doesn't > reference the <<Status (Current Groups)>> function. (It shows as Status > (<<unknown>>). In fact, that function isn't available in the > Scriptmaker list of status functions, though other status functions are > available. This status function is also absent when creating new files, > so it appears to be related to FMP and not just ebase. > > This problem occured after an optimization of the hard drive, and I know > that this group has copies of both FMP3 and 4 on their machine. I'm > wondering if this could be a problem related to FMP3. Is the Status > (Current Groups) function a part of FMP3? Is there another problem that > could cause this? > > BTW, groups and passwords in ebase all appear to be correct. > > Carl Paulsen > ------------------ 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 ---------------------------------------------------------------------
