LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 1003 on application build

I have an application that runs from LabVIEW, but I can not make an exe. The project uses the database toolkit and LV 6.02. When I delete the database toolkit calls, I can build an exe.

I save all. Then I save for application build. When I close the source to build the application, I get a message "Save changes to DB Tools Parser.vi?". When I press explain, it says "VI Recompiled". Since I already saved all, this doesn't make any sense to me. I have also tried opening the offending VI, and saving it, but it doesn't help.

When I try to build the application, I get:
Error 1003 occurred at C:\project dir\exe build dir\internal.llb\DB Tools Parser.vi
Possible reasons: The VI is not executable.

I have re-installed both the
application builder, and the DB toolkit from replacement CDs. I have tried this on Windows NT, and Windows 98. I even re-formatted a hard drive, and built a clean install of Windows 98 with only LabVIEW installed. I get the same results on every test.

A NI technical support person CAN build the exe from my source files including the database calls. So I think my source code is OK.

I am stumped. Any ideas? All that's left that I can think of is to re-install LV 6.02 from new CDs, however it seemed that the problem was probably in the database toolkit, or the application builder, and I have already re-installed them from new CDs.

Thanks in advance for any help or ideas.
Bill Kemmerer
0 Kudos
Message 1 of 2
(3,074 Views)
I received this error in two different cases:

1. When my EXE included calls to an OCX that called an external OCX. This was solved when I went through and resaved all of my sub-VIs that included the OCX calls.

2. When I used the DB Toolset and did not do a mass compile first, including a save of the relevant DB Toolset VIs to my "source" directory.

I don't use LLBs but, instead, keep a separate "Development" directory for each target EXE. Saving ALL of the relevant VIs in that directory and referencing that for my build solved all of the 1003 errors during build.

I hope this helps.

val
0 Kudos
Message 2 of 2
(3,074 Views)