Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!news.swapon.de!aioe.org!.POSTED!not-for-mail From: Helpful Harry Newsgroups: comp.databases.filemaker Subject: Re: EventScript Plugin Serious Problem Date: Tue, 04 Aug 2015 16:19:45 +1200 Organization: Aioe.org NNTP Server Lines: 42 Message-ID: <040820151619452001%HelpfulHarry@BusyWorking.com> References: <14b533d3-5c74-4307-8f03-b9fc526c0fc7@googlegroups.com> NNTP-Posting-Host: eeJYT9Il4Ijpt4FG4X0lww.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Thoth/1.8.4 (Carbon/OS X) X-Notice: Filtered by postfilter v. 0.8.2 X-Face: vIZzK[X\z-._]-_:U?l@cBtwg<{a>ggn\mH}Vs>38E,#R%7h%U0'=4;1Q=erO %[T#a{YJfGvAbWmE@f_h], Keith wrote: > Hi Group, > > I've got an EventScript Plugin problem & could use some help. > > I tried opening my V13 Database in V14 & everything seems to have gone fine. > > However, I did a Recover in V14 : > > - No EventScript Plugin Installed : > > 64-Bit : 'Warning ...' Error > 32-Bit : 'Warning ...' Error > > - Plugin Re-installed : > > 64-Bit Warning ...' Error > 32-Bit : No Warning ...' Error : 'Recover built a new Database without > detecting any problems ...' > > By the way, the Recover produced the exact same Results in V13 > > Any insight would really help; the situation has me worried. I've never used the EventScript plugin, but it could be that it's not fully compatible with FileMaker 14. It could have corrupted a preference file (if there is one for the plugin) that needs re-creating, which is why FileMaker 13 is showing the same thing. I'm not sure how the plugin works, but it could also be a scrtip / script step or field somewhere that hasn't quite been fully recovered (e.g. if a script step says "EventScript(MyField)" and MyField no longer exists in the recovered database). That last message says "no Warning" and "without detecting any problems" ... I'd make a second backup of the database (hopefully you've still got one from before the recover just in case) and then see if it continues to work okay. Helpful Harry :o)