LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Access violation (0xC0000005)

Hello

I try to read all information about this error on forum but I did't find a solution.

I get thi error in application "exe" on second computer. I found that this error is generated after trying save "excel report" on disk. My program extract data from access file and place it into prepared earlier a template. before I try save I'm creating message to brake for a while execution and after save I do it again - and this is why I'm sure that this error is generating in this vi. 

Additional data:  I try it after Anty-wirus deactivation. The same results.

All I'm doing was done in administrator mode.

System where I create application (labview development..):

Windows 7 64 bit, labview 32 bit, Microsoft Office profesional 2010

Computer when I try this program:

Windows XP sp3 32 bity, office profesional 97.

In first computer this "exe" file work correctly with saving file on disk and closing.

Please help if someone know a solution.

 

Crash File information:

####
#Date: 10 sty 2013 08:06:36
#OSName: Microsoft Windows XP Dodatek Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: DPv4_14
#Version: 11.0.1f1 32-bit
#AppKind: AppLib
#AppModDate: 01/09/2013 12:50 GMT
#LabVIEW Base Address: 0x30000000


2013-01-10 08:10:30.236
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash: Crash caught by NIER
minidump id: e521143e-8bc2-4729-bea6-46d2f571e478
ExceptionCode: 0xC0000005ÄN
0x3072D954 - lvrt <unknown> + 0
0x3072DD08 - lvrt <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x7C83AB50 - kernel32 <unknown> + 0
0x00000000 - DPv4_14 <unknown> + 0

0 Kudos
Message 1 of 8
(5,025 Views)

I check it in other computers: were is windows 7 and office 2010 it works, where is windows Xp and office 97 this not work. Right now I dont have other combination.

I create small program - test program with "MS word" report. The same situation - when I want use "save report to file" this generate error. 

0 Kudos
Message 2 of 8
(4,998 Views)

Can you attach the code which generates the error?

-----

The best solution is the one you find it by yourself
0 Kudos
Message 3 of 8
(4,986 Views)

Yes.. becourse I looking for solution the files are changing. I attache  a subVi  whitch is creatingf "Excel" report. This subVi is prepared to find place where error is creating so there are messages before and after "save report file". This subVi getting data from main program and paths. Excel templete have 6 or 7 workseets. 

Sorry for no clarity of this code

0 Kudos
Message 4 of 8
(4,970 Views)

I checked this program on computer with : windows Xp 32bity and office 2003. And it worked. so my conclusion is that this Vi dosn't work with offcie 97. 

0 Kudos
Message 5 of 8
(4,945 Views)

Hello gibon,

there is a knowledge base that describes the problem you are having:

http://digital.ni.com/public.nsf/allkb/D4D32D45EAD5830186256BD800506A41

 

The bottom line is, that Microsoft changed the ActiveX model which makes Office 97 and 2000 incompatible.

 

BR,

0 Kudos
Message 6 of 8
(4,878 Views)

aaa.jpg

It is not nice that I can't use this function.. but I found something similar (in foto above).

This work on computer with office 2010 and office 97.

Of course user have to "click" on button "save" to save file, but everything is prepared (path to save and file name).

 

By the way it is very strange that function depend on installed office. I know that  connection to office 97 and 2010 are different but I think this situation can be detected by some function and than can be choosen properly function to do "save". 

In my opinion application "exe" should work on many computers with windows and detect what windows have or should tell my what is wrong. I spend many time to understand and to avoid this problem. I cant install office 97 on my computer (ealier uninstall labview and after install again). This is too much work.

 

And many thanks for help, link to explain was very helpful.

0 Kudos
Message 7 of 8
(4,857 Views)

Hi gibon,

the files are detected, and proper files are installed on the development computer. The system requirements for the deployment computer are the same as for the development computer, and this is not limited only to LabVIEW. It is not expected that an older software version will be always forward compatible.

I am sorry this has caused you problems. Please do not hesitate to ask if you have further questions.

 

Have a great weekend.

 

Best regards,

0 Kudos
Message 8 of 8
(4,852 Views)