Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.databases.filemaker > #2386 > unrolled thread

EventScript Plugin Serious Problem

Back to article view | Back to comp.databases.filemaker

Contents

  EventScript Plugin Serious Problem Keith <francois7675@gmail.com> - 2015-08-03 18:58 -0700
    Re: EventScript Plugin Serious Problem Helpful Harry <HelpfulHarry@BusyWorking.com> - 2015-08-04 16:19 +1200
      Re: EventScript Plugin Serious Problem Keith <francois7675@gmail.com> - 2015-08-04 07:19 -0700
        Re: EventScript Plugin Serious Problem Helpful Harry <HelpfulHarry@BusyWorking.com> - 2015-08-05 09:04 +1200
          Re: EventScript Plugin Serious Problem Keith <francois7675@gmail.com> - 2015-08-05 09:13 -0700
    Re: EventScript Plugin Serious Problem Howard Schlossberg <howard@nospam.fmprosolutions.com> - 2015-08-05 13:22 -0700
      Re: EventScript Plugin Serious Problem Keith <francois7675@gmail.com> - 2015-08-05 15:59 -0700

#2386 — EventScript Plugin Serious Problem

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.

Thanks,

Keith

[toc] | [next] | [standalone]

#2387

In article <14b533d3-5c74-4307-8f03-b9fc526c0fc7@googlegroups.com>,
Keith <francois7675@gmail.com> 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)

[toc] | [prev] | [next] | [standalone]

#2388

> > 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)

Hi Again, Helpful Harry,

As usual, thanks for your rapid response.

My question is rather why do I get a Recover error when I remove the plugin & not when it's installed.

The plugin is not 64-bit compatible so FileMaker v14 must be set to 32-bit but that has little to do with the question.

Also, I'm interested in knowing if these 'Recovery Warnings' are 'full-proof' or can I continue using the file.

Keith

[toc] | [prev] | [next] | [standalone]

#2389

In article <6d17e770-b078-481f-a7e6-4444eee2031e@googlegroups.com>,
Keith <francois7675@gmail.com> wrote:
> 
> Hi Again, Helpful Harry,
> 
> As usual, thanks for your rapid response.
> 
> My question is rather why do I get a Recover error when I remove the plugin &
> not when it's installed.

My guess, and only a guess, would be that something needs the plug-in.
When it's missing the recovery doesn't completely work. Perhaps the
database is using the plug-in and the recovery process see it being
called, but can't find that plug-in actually installed.



> The plugin is not 64-bit compatible so FileMaker v14 must be set to 32-bit
> but that has little to do with the question.
> 
> Also, I'm interested in knowing if these 'Recovery Warnings' are 'full-proof' 
> or can I continue using the file.

Technically FileMaker's Recovery option is only there to allow you to
(possibly) get the data back from a corrupted database file, but the
file itself may still have problems and it's not advised to continue
using it as the main database. 

The official process is to recover the corrupted file, import its data
into a *fresh*, unused, backup copy of the original database structure,
then delete the recovered file when you're happy you've transferred
everything (or at least everything you can).

Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2390

On Tuesday, August 4, 2015 at 4:03:20 PM UTC-5, Helpful Harry wrote:
> In article <6d17e770-b078-481f-a7e6-4444eee2031e@googlegroups.com>,
> Keith wrote:
> > 
> > Hi Again, Helpful Harry,
> > 
> > As usual, thanks for your rapid response.
> > 
> > My question is rather why do I get a Recover error when I remove the plugin &
> > not when it's installed.
> 
> My guess, and only a guess, would be that something needs the plug-in.
> When it's missing the recovery doesn't completely work. Perhaps the
> database is using the plug-in and the recovery process see it being
> called, but can't find that plug-in actually installed.
> 
> 
> 
> > The plugin is not 64-bit compatible so FileMaker v14 must be set to 32-bit
> > but that has little to do with the question.
> > 
> > Also, I'm interested in knowing if these 'Recovery Warnings' are 'full-proof' 
> > or can I continue using the file.
> 
> Technically FileMaker's Recovery option is only there to allow you to
> (possibly) get the data back from a corrupted database file, but the
> file itself may still have problems and it's not advised to continue
> using it as the main database. 
> 
> The official process is to recover the corrupted file, import its data
> into a *fresh*, unused, backup copy of the original database structure,
> then delete the recovered file when you're happy you've transferred
> everything (or at least everything you can).
> 
> Helpful Harry  :o)

Thanks again, Helpful Harry,

I went to a 5-year-old bu & the same error appeared !

It's getting quite complicated.

Any other thoughts ?

Keith

On Tuesday, August 4, 2015 at 4:03:20 PM UTC-5, Helpful Harry wrote:
> In article <6d17e770-b078-481f-a7e6-4444eee2031e@googlegroups.com>,
> Keith wrote:
> > 
> > Hi Again, Helpful Harry,
> > 
> > As usual, thanks for your rapid response.
> > 
> > My question is rather why do I get a Recover error when I remove the plugin &
> > not when it's installed.
> 
> My guess, and only a guess, would be that something needs the plug-in.
> When it's missing the recovery doesn't completely work. Perhaps the
> database is using the plug-in and the recovery process see it being
> called, but can't find that plug-in actually installed.
> 
> 
> 
> > The plugin is not 64-bit compatible so FileMaker v14 must be set to 32-bit
> > but that has little to do with the question.
> > 
> > Also, I'm interested in knowing if these 'Recovery Warnings' are 'full-proof' 
> > or can I continue using the file.
> 
> Technically FileMaker's Recovery option is only there to allow you to
> (possibly) get the data back from a corrupted database file, but the
> file itself may still have problems and it's not advised to continue
> using it as the main database. 
> 
> The official process is to recover the corrupted file, import its data
> into a *fresh*, unused, backup copy of the original database structure,
> then delete the recovered file when you're happy you've transferred
> everything (or at least everything you can).
> 
> Helpful Harry  :o)

[toc] | [prev] | [next] | [standalone]

#2391

If the EventScript plugin is not installed, then the Recover routine is 
trying to recover for an unknown function.  I would guess it is a bit of 
a false error.

That said, the old EventScript plugin (assuming it is the one from S4H) 
is not likely compatible and is definitely no longer supported by its 
developer.  I used to use that one extensively but have since switched 
all my solutions over to the (also free) one from Base Elements 
<http://www.goya.com.au/baseelements/plugin>.  Of course many of the old 
plugin calls can now be handled by FM's built-in script triggers, but 
there are still some cases where there isn't a built in script trigger 
to handle what I need.


On 8/3/2015 6:58 PM, 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.
>
> Thanks,
>
> Keith
>

[toc] | [prev] | [next] | [standalone]

#2392

On Wednesday, August 5, 2015 at 3:22:42 PM UTC-5, Howard Schlossberg wrote:
> If the EventScript plugin is not installed, then the Recover routine is 
> trying to recover for an unknown function.  I would guess it is a bit of 
> a false error.
> 
> That said, the old EventScript plugin (assuming it is the one from S4H) 
> is not likely compatible and is definitely no longer supported by its 
> developer.  I used to use that one extensively but have since switched 
> all my solutions over to the (also free) one from Base Elements 
> <http://www.goya.com.au/baseelements/plugin>.  Of course many of the old 
> plugin calls can now be handled by FM's built-in script triggers, but 
> there are still some cases where there isn't a built in script trigger 
> to handle what I need.
> 
> 
> On 8/3/2015 6:58 PM, 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.
> >
> > Thanks,
> >
> > Keith
> >

Thank you, Howard, that makes me feel a little better.

I took out the EventScripts from the Field Definitions, made a clone, reinstalled V13 & V14 only to have the same 'Warn ... Error' appear in both versions.

So, you think there is a possibility that it is a 'false alarm' ?

Also, thanks for the BaseElements' URL but I think I'll stay with internal Script Triggers for now.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.databases.filemaker

csiph-web