Finch1 Posted August 4, 2015 Share Posted August 4, 2015 Hello, 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, this prompted me to do a Recover in V13 which produced the exact same Results ! Thank you for any insight, Finch Link to comment Share on other sites More sharing options...
AHunter3 Posted August 4, 2015 Share Posted August 4, 2015 You should never run Recover to fix problems in your database. Recover is good for two things: a) When you know for sure your database file is hosed (because it won't open), Recover will let you pry it open and then you can export the records from it, to import into a replacement structure such as a known good clone from before the corruption/crash or a newly designed replacement structure; and b) When are you uncertain of the condition of your database and want to verify it. If it passes verification it is safe to continue using it. Meanwhile, did you make sure that the EventScript plugin is, in fact, installed in FileMaker 14? You do realize that plugins are not installed in database files but instead are installed in the FileMaker application itself? Plugins are to be found in the FileMaker Pro Version Number /Extensions folder. If it is installed, launch FmPro 14 and go to the Preferences dialog, plug-in tab. Is this plug-in enabled? If not, enable it here by checking the checkbox then quit & relaunch FileMaker. If it is enabled and you still get these error messages, I'd contact the plugin vendors to inquire about v14 compatibility. Link to comment Share on other sites More sharing options...
Finch1 Posted August 4, 2015 Author Share Posted August 4, 2015 Thank you very much for your reply. Please let me explain further. I wanted to get rid of this Plugin because it does not function in 64-Bit Mode. My goal was to replace it with Script Triggers; my attempts on a copy seemed to work. While the Plugin was in the Filemaker folders (V13 & V14), I opened the 2 Versions (separately, of course). The Plugin worked with V13 & only in 32-Bit Mode in V14 I then removed the Plugin from the 2 Filemaker folders & ran a Recovery, both failed, producing Warning Errors. I understood you to say that if I want to verify the condition of my database, I can run the Recovery system. Are the errors produced indicative of malfunction ? They also appeared on Back-Ups going back 10 or 15. Also, I was wondering why the error is not produced in V13 & V14 (In 32-Bit Mode) when I add the plugin back to the folder. I am wondering what is 'corrupted'. The Plugin has not answered my requests for info. Thank you again for your response, Link to comment Share on other sites More sharing options...
AHunter3 Posted August 5, 2015 Share Posted August 5, 2015 That does sound odd. Can you post the entire Recovery error, verbatim? Link to comment Share on other sites More sharing options...
Finch1 Posted August 5, 2015 Author Share Posted August 5, 2015 Hello, I appreciate the suggestion but this site is viewed by the public & there is a great deal of private info in the log. Any other help would be more than welcome. Thank you Link to comment Share on other sites More sharing options...
AHunter3 Posted August 5, 2015 Share Posted August 5, 2015 Do I correctly understand that FileMaker 13's Recovery reports no problem with the file when the plugin is installed? If so, the file is fine. Link to comment Share on other sites More sharing options...
Finch1 Posted August 5, 2015 Author Share Posted August 5, 2015 Yes, when the Plugin is installed, no problem in FileMaker 13's Recovery. Nor is there one in V14, if it's using 32-Bit Mode. Link to comment Share on other sites More sharing options...
AHunter3 Posted August 6, 2015 Share Posted August 6, 2015 My guess (admittedly only a guess) is that the Recovery process is evaluating the script steps that reference the plugin; and that when the plugin isn't installed, those script steps are unintelligible. Ideally, the Recover process should be smart enough to omit evaluations of External functions especially in scripts, but based on what you're describing, sounds like it isn't, and reacts to the script call External ("Unknown" "Unavailable, don't know what the heck is going on here") etc as a warn-worthy condition. But the file structure doesn't change with or without plugin so if it passes muster with plugin installed, the file itself is OK. Link to comment Share on other sites More sharing options...
Finch1 Posted August 7, 2015 Author Share Posted August 7, 2015 Thank you for the explanation, it is as I thought except for one thing : I removed all traces (scripts) of the plugin & replaced them with my own script triggers. Same problem. I then removed all the script triggers & the Recovery cited the same error. I'm just about ready to accept the warning. Link to comment Share on other sites More sharing options...
AHunter3 Posted August 8, 2015 Share Posted August 8, 2015 You can email me back-channel with the verbatim content of the warning you're seeing (with specific names of things that violate your confidentiality concerns replaced with asterisks if you wish), and I'll let you know if that clarifies anything. Link to comment Share on other sites More sharing options...
By Soliant Consulting,
By Soliant Consulting,
By Soliant Consulting,
Recommended Posts