Windows 7-32 bit, VS 2010 and Accpac 6.0 OCX

[vbdbcoder]

I can't seem to have luck with Windows 7 on my Accpac 6.0 integrated project in VS 2010. Any input please?

Development environment: Windows 7 (32 bit), only 1 Accpac 6.0, VS 2010, Sage Accpac SDK 5.5A .

In VS 2010, I created a windows app (.NET framework 3.5) project. I could add to my Toolbox 2 Accpac COM Components (ACCPAC DataSource Control 1.0 and ACCPAC FieldEdit Control 1.0). As soon as I dragged either one of the controls to my WinForm (Form1.cs), VS 2010 stopped responding and prompted me "Microsoft Visual Studio has encountered a problem and needs to close." I dugged deeper to the error source. It was coming from "nhandled exception at 0x1074d994 in devenv.exe: 0xC0000005: Access violation.".

 

[Jay Converse]

I maintain a VMWare XP image with VB 6.0. Develop and compile in XP, and it runs fine on Win7 32 and 64 bit. Yeah, VB 6.0 is over 12 years old in places, but it still works.

 

[ettienne]

I second that, VB6 & XP still works and beats messing around with VS problems.

 

[vbdbcoder]

Thanks a lot.

 

[vbdbcoder]

tuba and ettienne, are you guys DPP with Sage?

I sent my request to Sage. They require a DPP... I have been searching posts on internet from MSDN, Google... still can't get my IDE to work with accpac OCX. Frustrating...

 

[ettienne]

Yes on DPP... but you don't need the SDK to do OCX stuff.
There is a file you need to build to get OCXs loaded in anything other than VB6... hence the hint to stick with VB6. There are instructions on the official Sage Accpac VBA web site on what to do for VSS to get the OCX loaded.

 

[ettienne]

Refer to this post on the Sage Accpac site:

http://forums.sageaccpac.com/webforums/AspNetForums/ShowPost.aspx?PostID=97715