Leaderboard

In a few years you will have enough to make a Quilt or better yet a Cape (Champion CRELF)

So you want to print the source code to your application correct? Did you try File >> Print? Or File >> Print Window? If so what was wrong with doing that? You can also do it programatically using the Report Generation >> Easy Print VI Panel or Documentation

Ouch, silly mistake, thanks for pointing it out. Finally I could solve the problem. I found out that the error 505 generates when there's an error in the operation and then in another iteration of the same operation a no-error overwrites the error. I used the shift registers in the for loop, and noticed that now another error showed, saying that I was writing a duplicate of a primary key. So I checked the array I was writing to the DB and in fact I had stored data from the previous operations that I already wrote in the DB. After fixing that the problem was solved. Thanks!

So apparently you get a Virus for your 1000 Dollars?

I like her - that girl's got moxy. Although I'm wishing I hadn't have donated all of those ribbons to here - Otherwise I would have reached the floor by now. Oh well, I guess I'll have to come back next year.

For the record, the correct way to do this from scratch is: Pass a reference of LabVIEWClassControl (not LVClassLibrary) into the "vi object class" input of New VI Object Save the newly-created LVClassLibrary object to disk Pass the path of the LVClassLibrary into the "path" input of New VI Object

I've done this in the past. I found it easiest to use a template and change the controls as needed using scripting. Building it from scratch each time is a lot more work.

Sure, here you go. Saved in LabVIEW 2012. OS Window and Native Window properties.vi

It appears OS Window is deprecated - you may want to try Native Window. It outputs 64 bit handle rather than 32-bit, and the results seem to be equal (run this snippet):

Yair- Works! For our application, I just had to add a SetWindowPos (hWndInsertAfter = -1) afterward to keep the window in front (topmost)... Thanks for the help! Set Calling VI Wnd Topmost & Active.vi

You can try this. It has worked for me in the past. The key is attaching the thread's input.