bargraph style changes when app builder is used?

[RGM]

I'm going nuts trying to figure this one out...

I'm using a new control of a nice 3D bargraph ... I chose the style that has
"fills from the bottom to the current value". Everything looks good
however, when I run the App Builder to create an exe, it's now a bargraph
with a style of "no fill". I've tried adding a property node telling it
programatically that I want the "fill from bottom" style. No show!!!

Any ideas?

Bill

p.s. This was origianlly a LV 5.0.1 application... mass compiled into LV
6i...

[Darren]

Bill,

I have two ideas that might help you out. First, make a copy of your labview.ini file and rename it xyz.ini, where 'xyz' is the name of your executable. Then open up this copy and change the top line of the .ini file to [xyz] instead of [LabVIEW]...then put this modified xyz.ini file in the same folder as your executable. See if your bar graphs look ok now.

If this does not work, I recommend you update to LabVIEW 6.0.2 (if you have not already)...you can download this update from our website.

If neither of these suggestions help, please let me know, and attach a VI that demonstrates the problem (when built into an EXE) so that, if necessary, I can present the issue to our developers.

Thanks for your patience on this issue, and have a pleasant day.

Sincerely
,
Darren Nattinger
Applications Engineer
National Instruments

[RGM]

Darren,

Thanks for the response...

It appears that Greg McKaskle may have come up with the answer. I normally
never install the LV Run-Time Engine on to my target computer. For years
we've just copied the lvrt.dll & serdrv files into the same directory as our
application.

I guess that works fine for classic controls, right?

When I copied the entire \program files\national instruments\shared\labview
run-time\6.0 directory into the target system directory with our
application, everything came up fine. I know I'm still not "installing" it
into
Win98... is there a bunch of registry entries that I would still be missing?

Is there any good source of info on what files are for what? I assume they
aren't copiled into the application exe because you want to allow multiple
LV applications to run with common libraries, right? Or is there other
reasons? Maybe that should be an option?

As for your suggestion about the ini file, we've wondered where to find more
details about the ini? We have three lines in our ini file:

[program name]
anxiousMemoryDeallocation=True
postScriptLevel2=False

I remember we were having some memory problems back on a K6-2/300 machine
with only 32Meg of RAM. We now install 64Meg on all units and our app seems
to like it. As for the postscript line, you got me!!?

Thanks,
Bill

p.s. I have downloaded the 6.0.2 update, but haven't had time to install it
yet.

-----

Darren wrote in message
news:506500000005000000EC320000-993342863000@exchange.ni.com...
> Bill,
>
> I have two ideas that might help you out. First, make a copy of your
> labview.ini file and rename it xyz.ini, where 'xyz' is the name of
> your executable. Then open up this copy and change the top line of
> the .ini file to [xyz] instead of [LabVIEW]...then put this modified
> xyz.ini file in the same folder as your executable. See if your bar
> graphs look ok now.
>
> If this does not work, I recommend you update to LabVIEW 6.0.2 (if you
> have not already)...you can download this update from our website.
>
> If neither of these suggestions help, please let me know, and attach a
> VI that demonstrates the problem (when built into an EXE) so that, if
> necessary, I can present the issue to our developers.
>
> Thanks for your patience on this issue, and have a pleasant day.
>
> Sincerely,
> Darren Nattinger
> Applications Engineer
> National Instruments