Sage 100

I'm trying to create a System DSN using the MAS 90 4.0 ODBC driver. The USER DSN installed by the MAS client works ok, but SYSTEM DSN's all time out after 45 seconds on my workstation, and even when creating it right on the MAS database Server. Settings I've tried include: Basic Tab Name: DEM Database Directory: \\main\sage\mas90\ as well as f:\mas90 Definition file: {blank} Server Tab Server Name: Tried name as well as it's IP TCP/IP Port: 10000 Logon Tab Company Code: Tried all company codes Default userID: administrator as well as {blank} Password: XXXXXXXXX as well as {blank} Session ID: test, test1, 111 and {blank} Options Tab Prefix for Data Files: \\main\sage\mas90\sy\, \\main\sage\mas90\==\ Path to Views DLL: \\main\sage\mas90\home\ Dirty Read: Y and N Burst most: Y and N Strip Trailing spaces: Y and N Cache Size: 4, 10 Connection String: DSN=COMPANY; UID=administrator; PWD=XXXXXXXX; Directory=\\main\sage\mas90; Prefix=\\main\sage\mas90\sy\, \\main\sage\mas90\==\; ViewDLL=\\main\sage\mas90\home\; Company=COMPANY; LogFile=\PVXODBC.LOG; RemotePVKIOHost=main; RemotePVKIOPort=10000; CacheSize=10; DirtyReads=1; BurstMode=1; StripTrailingSpaces=1; SERVER=NotTheServer These variations attempted on the server and my admin workstation timeout after a minute with this same result: Connection failed. [ProvideX][ODBC Driver][ISAM]ISAM communication error. Is there a trick to this that I'm missing?

leave the server tab blank.I think that is your porblem also hit apply and close and re-open the DSN before hitting test (I think that was on earlier servers but won't hurt to do it)

also session ID should be blank (you tried taht but leaving it blank is the right choice there)

@DavidOverholt is correct. Also in the Options tab, to buy a little bit of speed you don't need the Prefix for Data Files (only MAS itself needs it in the SOTAMAS90 DSN) and don't needs Path to Views DLL (unless you want to use the BI Reporter views - those are the tables starting with letter ""v""). Also good idea to click Silent in Options tab as there are a few places where the ODBC Database Logon dialog doesn't suppress despite entering the UserID, pswd, and Comp Code.

@AlnoorCassim Thanks - I never knew about the ""silent"" option - but I have been stricken by it once or twice. I'll keep that one in my frontal lobe for future reference!

@David - It works! Thanks to you and also to @Alnoor for the tip on the ""silent"" option as that will be handy too.