Make Troi Dev License Work in Runtime

[Mark L]

Newbie-ish Question:

Back in April, I was 100% convinced I needed the Troi Text Plug-in and I plunked down the $139 for the Windows Developer version. I installed it into my FMP Dev 7 and worked with it a bit - it's really quite neat. To make a long story short, I actually was able to do most of what I intended the plug-in for without it - until I hit a wall the other day - and now I need to incorporate it into my application.

No big deal you say - and you are probably right - except I can't get it to work in my runtime version. What do I need to do differently so it will work in a runtime version of my program? I asked their support - but they just refer me to a web page that doesn't seem to have the answer - at least as far as I can tell.

I feel like an idiot, and maybe I am - but I still need to resolve this - so I'd appreciate your help.

Thanks in Advance,

Mark

[RalphL]

Have you installed a copy of the Plug-in into the Extensions Folder of the Windows Solution Folder? Has it been enabled in the Preferences dialog box?

[Mark L]

Hi Ralph -

Thanks for checking in on this.

Yes on both accounts - and the proof would be that Troi wouldn't work on my PC without these - correct?

Remember my install of Troi Text Plug-in on my FMP Developer 7 works fine, it's just the runtimes created by it where it doesn't work.

Thanks,

Mark

Edited September 20, 2005 by Guest
Clarified.

[Zero Tolerence]

What hes asking is if in the folder that you bound your runtime in (The folder where the actual runtime application is) there is an extensions folder, you ALSO have to have your copy of the plug-in installed there. Just copy and paste it and it should work fine.

[Mark L]

Zero Tolerance-

Thanks for replying.

OK, I get that now - so I did it and now I'm a step further along. Now when I go to the layout where the Plug-in is used, I get a "unlicensed" message - saying I have 30 days to register. The runtime still calls the same start-up script that pulls my license info used on my PC (and it's a developer license) - what I am I still missing?

Thanks again,

Mark

[RalphL]

Without seeing the text of your script, it is difficult to say what is wrong. But I would bet that it is in the text used in the set field that is used for checking the version.

[SteveB]

Are you initializing the plugin by calling the function that returns the plugin's version #?

Steve

[Mark L]

Ralph-

It looks like this:

Set Field [ForPluginStartup::gForPluginStartup: External ("xfrm-Version";"My Company Name, Inc.|zzzz-yyyy-xxxx-wwww-V")]

Set Field [RegiFunc::gVersion; RegiFunc:${TrText_Version}]

Hopefully, I've recreated the code well.

Obviously the company and actual license code are changed.

Also note that I have two Tables (whoa, I only thought I had one?? Can't remember how I came to that) As seen above - one called ForPluginStartup - which has 2 fields and no records. Fields are:

gForPluginStartup (Text/Global) ForPluginStartup_Format (Text)

The second table is called RegiFunc and has the following fields (also no records: )

gErrorCode (Text/Global)

gDescriptionHelpText (Text/Global)

gWindows RegString (Text/Global - Auto-enter Calculation - which is the stuff pasted from the Troi licensing e-mail)

gVersion (Text/Global)

TR_Text_Version Auto-enter calculation:=gWindows RegString

I just noticed that the previous field is not global - would that affect things?

Thanks in advance again,

Mark

[RalphL]

RegiFunc is a file supplied by Troi to help you set up the string for regestering the plug-in.

The string should have a #Begin & a #End. It sounds like you may have that in gWindows RegString.

[RalphL]

Shouldn't you be using the TrText-Version function?

[Mark L]

Ralph-

I have the following in that field (doctored a bit of course )

"#BEGIN TroiText2

Registered-To: Mxxx Xxxxxxxxx

This Troi Text Plug-in for Windows may only be used by end-users of Mxxx Xxxxxxxx

#SIGNATURE TroiText2 AAAAAA-AAAAAAAAAAAAAAAAAAAAAAAAA

#END"

[Mark L]

Shouldn't you be using the TrText-Version function?

I'm not sure I follow you on this - ?

(Also as I keep repeating - all works fine as is, on my PC, it's just the runtimes that now read "License Expired..." etc, etc.)

-Mark

Edited September 20, 2005 by Guest

[RalphL]

Have you added a Troi Payment Certificate to the FileMaker Folder? This would Setup the plug-in without your script.

Set Field [ForPluginStartup::gForPluginStartup: External ("TrText_Version" ; "#BEGIN TroiText2

Registered-To: Mxxx Xxxxxxxxx

This Troi Text Plug-in for Windows may only be used by end-users of Mxxx Xxxxxxxx

#SIGNATURE TroiText2 AAAAAA-AAAAAAAAAAAAAAAAAAAAAAAAA

#END" ]

This should return a zero in the field ForPluginStartup::gForPluginStartup.

I don't see a need for the RegiFunc table.

[Mark L]

Have you added a Troi Payment Certificate to the FileMaker Folder? Yes, I did (back in April) add TroiPay.txt and put it in FM folder.

Set Field [ForPluginStartup::gForPluginStartup: External ("TrText_Version" ; "#BEGIN TroiText2

Registered-To: Mxxx Xxxxxxxxx

This Troi Text Plug-in for Windows may only be used by end-users of Mxxx Xxxxxxxx

#SIGNATURE TroiText2 AAAAAA-AAAAAAAAAAAAAAAAAAAAAAAAA

#END" ]

This should return a zero in the field ForPluginStartup::gForPluginStartup.

I don't see a need for the RegiFunc table.

Ralph-

As to the Troi Payment Certificate - I did create TroiPay.txt back in April and did add it to my FileMaker directory. My guess is that it was/is successful. This would explain why Troi works on my FMP Developer DB – but not on the runtimes. Obviously on the runtimes, my attempt to validate the license is failing.

As to your next instructions, I’m a little confused by the "Set Field" info - isn't that to go in a script? (In spite of you saying no script was necessary. I attempted to do the step above in a Startup script – and it didn’t seem to work – which is probably no surprise to you.) So where do I use the “Set field” you have written above (obviously using my proper licensing info in place of the mock up.)

Thanks for your persistence,

Mark

[RalphL]

I don't recall saying no script is necessary. SetField is a script step.

I would start by moving the Troi Payment Certificate from the FileMaker Folder.

Then I would use the RegiFunc.fp7 file found in the "For Solution developers" folder. Enter your data as per the e-mail from Peter.

This should validate the license.

Look at the scripts in RegiFunc.fp7, they should help you set up your scripts.

[Mark L]

[color:red]RALPH - I GOT IT!

Ok - so this has to go into the all time stupidest blunders on the Forum: I had created the RegiFunc table - but never put a record it in. So all my calculations/changes didn't work - becuase the data record was effectively empty!! I simply created a record - and now, per Troi's instructions, the Set Field[RegiFunc::gErrorCode: TrText_Version( RegiFunc::gWindows RegString )] works fine!!

[color:red]THANKS AGAIN RALPH - For hanging in here with me, until my thick brain got it!!-Mark

[RalphL]

You are welcome, glad it is working.