Using Month Calender of .net in Labview .

[Santu]

Hi Mathan,

Open Windows Explorer, goto Tools--> Options--> View tab --> Uncheck "Hide extensions for known file types", if it is checked.

Now, you ll get to see the .txt extension of the file I ve attached. Remove txt & replace with  exe file extension. Thats it.

This is done because forums will not allow exes to be uploaded as such even if zipped.

[Santu]

Now, I wish to know how did you do it in DOS prompt?

[Mathan]

Dear santu,

If you are using windows,

Click start menu--> select run--> type cmd and press enter--> follow as like in my attachment.

I have saved .txt file in my desktop initially.

Hope u understand????

Thanks,

Mathan

[Eriquito]

Hi Santu,

I do see the error you're talking about.  As you can see from the attached exe that I built on my system (you will also need to rename the txt to exe), it builds just fine...

I'd love to know exactly what setting/corrupt system file/etc on your system is causing the problem so that I can report it to R&D, but the easiest solution to you may be to simply do a complete uninstall and reinstall of LabVIEW and whatever addons/drivers/toolkits you have.  My guess is, this will correct the problem.

[Santu]

Hi Eric,

The specified error occurs with exe ( when .net month calendar is used ) when , an option in Application Builder->Avanced Category  "Enable Enhanced DSC Run-Time Support" is checked .

We are using DSC Module 8.5.1 so we used to check this option when building an executable with App Builder. Then it was not giving such error with exe .

Now we  are using .net Month Calendar in the same project , we are getting this error.

But when  "Enable Enhanced DSC Run-Time Support" is not checked, the exe is not giving any error when run! !!!!.

What  is the relation of using .net control with  "Enable Enhanced DSC Run-Time Support" option.We are using Labview 8.5.1. I am attaching the option screen.

regards

Santosh Kumar

[Eriquito]

Hi Santu,

The error does not occur on mine in 8.5.1 even when I have that option checked.

Enabling this option causes the EXE to use more resources than it normally would, including reducing the start-up performance and increasing the file size.  It wouldn't surprise me if it also required more memory to compile, and that it is somehow related to your issue.

FYI, you usually don't need to check that box.

From the LabVIEW Help - Advanced Page (Shared Library) :


"Enable Enhanced DSC Run-Time support—This option only appears if you have the LabVIEW Datalogging and Supervisory Control (DSC) Module installed. Builds the application with the enhanced LabVIEW (DSC) Module Run-Time Engine. The DSC Module Run-Time Engine adds additional support for programmatic project library and shared variable management in applications that you build with the DSC Module. You must place a checkmark in this checkbox in the following situations:

    * The application you want to build uses VI Server references to modify a library file programmatically.
    * The application you want to build uses the Save to Library VI."


Unless you get error code 1055 when you try to compile without having that box checked, you don't need it, so for now I would recommend just leaving it unchecked.

[inversion]

Hello Eriquito,

I am also having the same issue now.. i open my main VI and it reports

1. LabVIEW needs more memory to compile VI.

2. There is a problem with a subVI but this VI has no block diagram!

When i try to open the block diagram, it wont open... various menu items are also greyed out including the show block diagram.

Before I open the file its size is 944 KB and after saving the same file it reduces down t 457 KB!!! Good job that I have a backup.

The only thing i can think of is the change of computers... I was developing my app on my work PC where it was working fine, then took it home as i normally do and this occurs. I know that some of the subVI's in my instr.lib folder might be slightly different from my work PC but I can just ignore these as I normally do until I get back to work... Ive been doing this alot, but never has this happend to me.

I will try again at work tomorrow and post back.

Greetings

Alex.