dbTalk Databases Forums  

Plug-in doesn't work with Bound Runtimes

comp.databases.filemaker comp.databases.filemaker


Discuss Plug-in doesn't work with Bound Runtimes in the comp.databases.filemaker forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Carl Mittler
 
Posts: n/a

Default Plug-in doesn't work with Bound Runtimes - 07-16-2004 , 09:56 PM






I use a Troi File Plug with a FM6 Solution. I would like to try it out in a
Runtime Version. In testing, everything appears to work fine...except the
Troi File plug-in. (I use it to find the path of external documents on the
hard drive and set a field to that path). Does Dev Tools automatically
move over the plug-in during the Binding process ? I can not find any
documentation on this. Am I missing something here. Thanks, I'm new to
Runtimes.
Carl



Reply With Quote
  #2  
Old   
Michael Myett
 
Posts: n/a

Default Re: Plug-in doesn't work with Bound Runtimes - 07-16-2004 , 10:48 PM






Carl Mittler wrote:
Quote:
I use a Troi File Plug with a FM6 Solution. I would like to try it out in a
Runtime Version. In testing, everything appears to work fine...except the
Troi File plug-in. (I use it to find the path of external documents on the
hard drive and set a field to that path). Does Dev Tools automatically
move over the plug-in during the Binding process ? I can not find any
documentation on this. Am I missing something here. Thanks, I'm new to
Runtimes.
Carl


Create a subfolder under your bound solution folder called "system" and
copy the Troi File Plugin there. I believe Troi plugins work with bound
solutions, although this is not always the case with every plugin.

Michael Myett


Reply With Quote
  #3  
Old   
Helpful Harry
 
Posts: n/a

Default Re: Plug-in doesn't work with Bound Runtimes - 07-16-2004 , 11:58 PM



In article <pJWdnQqOhKwUPGXdRVn-hQ (AT) adelphia (DOT) com>, Michael Myett
<michael.myett (AT) adelphia (DOT) net> wrote:

Quote:
Carl Mittler wrote:
I use a Troi File Plug with a FM6 Solution. I would like to try it out in a
Runtime Version. In testing, everything appears to work fine...except the
Troi File plug-in. (I use it to find the path of external documents on the
hard drive and set a field to that path). Does Dev Tools automatically
move over the plug-in during the Binding process ? I can not find any
documentation on this. Am I missing something here. Thanks, I'm new to
Runtimes.
Carl

Create a subfolder under your bound solution folder called "system" and
copy the Troi File Plugin there. I believe Troi plugins work with bound
solutions, although this is not always the case with every plugin.
It's been a while since I've had to do plug-ins with a runtime, but I
think on the Mac the folder needs to be called "FileMaker Extensions"
and be in the same folder as the runtime application.

Most plug-ins SHOULD work with runtime applications, as long as the
programmer followed the rules. )

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)


Reply With Quote
  #4  
Old   
Carl Mittler
 
Posts: n/a

Default Re: Plug-in doesn't work with Bound Runtimes - 07-17-2004 , 05:55 PM



You guys are the greatest. I was missing something - A "system" folder
Thanks to all, this group has taken me out of another jam.
Carl





"Helpful Harry" <helpful_harry (AT) nom (DOT) de.plume.com> wrote

Quote:
In article <pJWdnQqOhKwUPGXdRVn-hQ (AT) adelphia (DOT) com>, Michael Myett
michael.myett (AT) adelphia (DOT) net> wrote:

Carl Mittler wrote:
I use a Troi File Plug with a FM6 Solution. I would like to try it
out in a
Runtime Version. In testing, everything appears to work
fine...except the
Troi File plug-in. (I use it to find the path of external documents
on the
hard drive and set a field to that path). Does Dev Tools
automatically
move over the plug-in during the Binding process ? I can not find
any
documentation on this. Am I missing something here. Thanks, I'm new
to
Runtimes.
Carl

Create a subfolder under your bound solution folder called "system" and
copy the Troi File Plugin there. I believe Troi plugins work with bound
solutions, although this is not always the case with every plugin.

It's been a while since I've had to do plug-ins with a runtime, but I
think on the Mac the folder needs to be called "FileMaker Extensions"
and be in the same folder as the runtime application.

Most plug-ins SHOULD work with runtime applications, as long as the
programmer followed the rules. )

Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.