Custom Accpac Applications in 64 bit OS

[vbdbcoder]

Has anybody successfully created and deployed Accpac custom application (for Accpac version 55, 56, 60) for 64 bit windows?

Any pointer on how to work on\around 64 bit is highly appreciated.

My app works fine on 32 bit windows (XP or Windows 7). But it does not seem to work for me on 64 bit windows. I have SM, OE1100 ocx, PO1200 ocx in my project's reference.

On 64 bit windows (even in development machine). The code craps out at the system manager session init event. ocx can't be imported.

 

[Jay Converse]

Accpac is a 32-bit app. Compile it in a 32-bit virtual session.

 

[ettienne]

Delete *.ecx in all folders on the computer where it will not run. These are temporary files created when the app runs the first time and cause problems if you use a new ocx.

 

[ettienne]

Btw do a del *.ecx /s from a command prompt, Windows Explorer is not great for finding and deleting these files.

 

[vbdbcoder]

Hi tuba2007,

I have no problem in coding, compiling and installing the app in 32 bit.

My development environment is 32 bit windows 7 with VS 2010. I develop in .NET and code in C#. Things are all good and nice in 32 bit environments (both development and production). When I install the project on a 64 bit machine, I keep getting the problems.

I believe VB6.0 might be able to get around the grief. But I have switched to C# and .NET framework for 99% of the work. If I have to keep VB6.0 only for 64 bit deployment, due to Accpac ocx or dlls limits, it might be more costly to maintain.

Any thoughts?

 

[Jay Converse]

I maintain a VMWare XP image with Accpac 6.0, and VB 6.0. The only "cost" is the minute or so it takes to boot the image. I haven't had any call from my clients to move to VS 2010.

 

[DjangMan]

I'm on a 64-bit dev machine writing 32-bit apps that sit on 64-bit servers.

Make sure that you have enabled strong names for .net.

 

[vbdbcoder]

Hi DjangMan,

Do you run the accpac integrated 32 bit app on the 64-bit server as well? If you do, then ... please provide more details on how to make it to run on a 64 bit windows.

I can have an installed file on the 64 bit server and have my 32 bit client machines to run the app.

I don't give my assembly a strong name.

Thanks

 

[DjangMan]

Accpac will run on a 64-bit computer without any special setup. The operating system will detect that Accpac is a 32-bit application and will run it appropriately.

You do have to make sure that if you are using an ODBC connection to the database that you use the 32-bit ODBC Administrator.

Have you set your development environment to create a 32-bit executable instead of a 64-bit executable?

 

[vbdbcoder]

The executable I built is 32 bit (for x86 platform).

Simple code like the below (to grab the logged-in session) failed on 64 bit development environment. It failed at the .Createsession line.

AccpacSessionManager.AccpacSessionMgr vSessionMgr = new AccpacSessionManager.AccpacSessionMgr ();
AccpacCOMAPI.AccpacSession vSession = new AccpacCOMAPI.AccpacSession();

string sUser = "";
string sCompany = "";
string sCompany2 = "";

vSessionMgr.AppID = "XX";
vSessionMgr.AppVersion = "60A";
vSessionMgr.ProgramName = "XX1000";
vSessionMgr.ServerName = "";

vSessionMgr.CreateSession ("", 1, out vSession);

vSession.GetSignonInfo (out sUser, out sCompany, out sCompany2);

These code are what I use for basically all projects to get the logged-in session from SM. It works in 32 bit