Sage 100

OK, is it just me? I access mas data through vb scripts all the time. But...I'm currently working in a MAS200 - 64 bit environment. When I try to create a connection back to the MAS data using the 32 -bit ODBC driver windows give me an error. Anyone else run into this yet? Am i missing something?

Can you post the relevant portion of the script?

Sure, this is just a ""dumbed down"" version i quickly created to try to get to the bottom of the issue. I usually use a connection string more like the one that is commented out. The other one is copied directly from the ODBC connection test window. dim conn, rs, sql, discount, linedisc, strCustNo, strVendNo, strAltDiv, strCustDiv strCustDiv = ""01"" strcustNo = ""0000010"" set conn = CreateObject(""ADODB.Connection"") 'conn.open = ""DSN=SOTAMAS90;UID=NEO;PWD=;Directory=\\server02\e$\Sage\Version45\MAS90;Company=RCI;Cachesize=4;DirtyReads=1;BurstMode=1;SERVER=NotTheServer"" conn.open = ""DSN=SOTAMAS90; Directory=E:\MAS90; Prefix=E:\MAS90\SY\, E:\MAS90\==\; ViewDLL=E:\MAS90\HOME; LogFile=\PVXODBC.LOG; CacheSize=4; DirtyReads=1; BurstMode=1; StripTrailingSpaces=1; SERVER=NotTheServer"" sql = ""select * from AR_Customer where ARDivisionNo = '"" & strCustDiv & ""' and CustomerNo='"" & strcustno & ""'"" set rs = Conn.Execute(sql) if not (rs.bof and rs.eof) then msgbox rs(""CustomerDiscountRate"") else msgbox ""Nothing"" end if

Additional info: I manually ran the script using c:\windows\syswow64\cscript.exe (32-bit script engine) and it worked like a charm. I'm afraid I might be out of luck. I wonder if there are any plans for a 64-bit SOTAMAS odbc driver?

Version 5.0 is supposed to have a 64-bit ODBC driver.

Thanks Dawn. That's good to know. Not sure what I'm going to do about my current situation but that's still good to hear.

What is your current situation? Whay can't you invoke the 32-bit script engine?

I'm running an old fashioned button script. Can I specify the 32-bit script engine? MAS just launches the script how do I specify?

It's odd that one can run the 32-Bit version of Notepad with a parameter from ..\SysWoW64 but not the 32-bit cscript.exe or wscript.exe. I wonder what's up with that. You could change the default program that is loaded for the .vbs file type to cscript.exe in SysWoW64, but that's likely not something you want t have to propogate around to all the users. If it is then - http://tinyurl.com/7892o2z

Thanks for the idea Dan, it's at least an option I can offer my client.