How to connect to MSS

So the connection to MSS in the asn is

MSS:DSN:database|user|password

You need a new DSN in the ODBC connections for each SQL server INSTANCE, not database. So as long as your databases are all in one instance, you only need to set up the ODBC settings on the client once. 

You can set up the odbc stuff by importing registry keys exported from another machine, as long as you are using a SQL server driver which is installed by default. 

We use advanced installer to build our installer exe, and it has the facility to check for the sql server driver, install it if necessary and then set up the ODBC client, and I would expect any sane msi/exe builder to do this. Alternatively, if you hand craft every client install, it's pretty easy. 

Also, in the client asn you can use TCP: (TLS:) to get the data via the urouter, and then set up the data driver on the server (as long as you don't use any third party stuff which needs access to the database (we use crystal reports)). 

Iain

Hi Paul
"Don't Panic" as Douglas Adams once said 🙂

a)On Windows, ODBC is "build in" so you don't have to install it but to configure.
Be aware to you use the correct the ODBC version i.e 32bit or 64 bit. It depends on your UnifAce installation not on the OS/Windows

b) Do you have one server with one DBMS (Microsoft SQL-Server) installed?
Then you have only to configure one ODBC connect

c) The databases (on one DBMS) can be assigned in ASN-File of UnifAce, no need for mulitply ODBC-configurations

ad a)
ODBC-64 bit  could be find under windows\\system32 → odbcad32.exe
ODBC-32 bit to be found in windows\\syswow64 → odbcad32.exe

[Yes, it's strange but correct. If anyone is intressted  into the story ... 🙂 ]

ad b)
Just open the ODBC manager and connect to the (windows) server and the to the DBMS-server
As database use any database on the server to which all clerks to have access
The ODBC-source should be named like <windows-server>+"_MSS"
Or <windows-server>+"_"+<DBMS-server>+"_MSS" (if there is more then the default server is installed

Test the connection and ODBC is done

ad c)

Im ASN-file, add the necessary paths

[PATHS]

$PATH1    MSS:SERVER01_MSS:MSS_DATABASE01||
$PATH2    MSS:SERVER01_MSS:MSS_DATABASE02||
$PATH3    MSS:SERVER01_MSS:MSS_DATABASE03||

Where PATH<n> is the path defined in the model or use the [entities] section

[DRIVER_SETTINGS]

USYS$MSS_PARAMS procs:off,ids:quoted,mapping:2,iso:rc,gran:row,os:96,hs:on,ri:uniface,stmtcache=off,locktime=120,mlw=3

[ENTITIES]

*.MDL_03 $PATH3:*.*

That's all folks 🙂

Ingo