Pot "verify" messes up data entry-Bug?- Others seen this?

[jpss]

---

Escrito por flexman:
This does NOT load with 4.51 lookout as purchased through Automation Direct. "error object class not loaded". Pot is then unavailable in object builder.

---

This is just a comment...

We use Lookout 5.0 build 7 and when I tried to use pot for 6.0 version I got the following error when lookout starts: "No se encuentra el ordinal 2791 en la DLL lkworks.dll" (please apologize my "Spanish Windows": here comes my free translation: "Can't find ordinal 2791 in DLL lkworks.dll")

After a couple of times trying to start lookout, it finally does it, but when I run a process which uses a pot the same error comes up.

With pot for 4.5.1 I got no problems.

JPSS

[A.S.]

Hi,
So it appears that the pot CBX for Lookout 4.5.1 works with Lookout 5.0 also. And the CBX for Lookout 6.0 works with Lookout 5.1. I will upload them again to the FTP site for clarity. Go to ftp://ftp.ni.com/outgoing/.

pot451.cbx : Lookout 4.5.1 and Lookout 5.0

pot60.cbx : Lookout 5.1 and Lookout 6.0

Simply copy the appropiate CBX to your Lookout folder (usually in c:\Program Files\National Instruments\Lookout x.x). Remember to move the existing pot.cbx file to another location for backup purposes in case you need to revert back.

Please let us know if you see any problems using the pot objects as suggested above. A more permanent fix will be implemented based on feedback.

Thanks!

[flexman]

This does seem to work reliably when newly creating objects.

I am trying to see if there any way to force the new version pot object to be used in an existing application with many (100) old_pots already created. I tried forcing a recompile by opening from lks file- the problem still exhibited.

Can you advise on:
1) forcing existing pots over to new cbx? (I'm accustomed to LKS text editing if there is a workaround there)
2) If the application is distributed in a secure compiled form ("protect from editing with password"- only lkp sent to endusers with runtime key) will it be necessary to include the new cbx on files that will not re-compile?

[A.S.]

Hi,

1) I guess I didn't mention this in my earlier posts. But you can actually rename the new CBX files you downloaded to pot.cbx (same as the original file). But again, make sure you remove the original pot.cbx to another folder to back it up. Once you do that, if you open the LKS file, Lookout should recompile the process. And thus it should start referencing the new file. I guess the key point is to rename pot451.cbx (or pot60.cbx) to pot.cbx.

2) It will be necessary to include the new CBX so the end user has it too. They can place it in the Lookout run-time folder and replace the old pot.cbx. They will not need to recompile, so the password protection is fine.

CORRECTION
pot451.cbx: Lookout 4.5.1, Lookout 5.0 & Lookout 5.1

pot60.cbx : Lookout 6.0

Hope this helps.