Hi DIGIMASTERS,

It seems the installation is not complete. 

Please note that if you want to use Sales Analysis Module , you need to create an empty UNISALES database with name equal to XXXXXXUNI where XXXXXX is the database name of the SAGE company . For instance , if you have DIGIDT as the name of the database for the company, the UNISALES data should be named DIGIDTUNI. Also, you should not add this DIGIDTUNI db to SAGE database setup.

Cheers 

Eudes

Hi DIGIMASTERS,

It seems the installation is not complete. 

Please note that if you want to use Sales Analysis Module , you need to create an empty UNISALES database with name equal to XXXXXXUNI where XXXXXX is the database name of the SAGE company . For instance , if you have DIGIDT as the name of the database for the company, the UNISALES data should be named DIGIDTUNI. Also, you should not add this DIGIDTUNI db to SAGE database setup.

Cheers 

Eudes

Hi Eudes,

yes we created XXXXXXUNI before loading data.

Thanks

only very few tables were created by activation:

Yes, it looks correct. These are the tables of Ops Inquiry. UXARINVH is a table of Sales Analysis . No UX table is shown. It looks as if no UX table was created and populated.
You should  have an ODBC DSN defined for this XXXXXXUNI database. Ensure the connection is successful.
Also, you are using driver 18 for SQL Server.  I use ODBC32 with Server Native Client 11.0 and it works fine. You may want to try it out.

Did you do the activation and setup of Sales Analysis?

Hi Eudes, are you saying we must created an additional 32-bit system DSN named XXXXXXUNI? and how and where will this DSN be used?

I have it defined on the server where SAGE is installed (in this case the database is installed on another server).

We finally used SQL query to create those tables. It's okay now.

Thanks to everyone.