ODBC .NET for MAS90 4.05 steps 1

[dcrussel]

We are looking at the time/effort it would take to pull specific information (orders, customers, etc) from the MAS90 system (4.05) into a MS SQL db.
The system will be written in .NET

Is there a FAQ about what is required to accomplish this?

1. Which ODBC driver? There was another post regarding the driver for 4.10. Can 4.05 utilize the same driver?

2. Table structure definitions?(beyond the trsg file structure info)

Thanks for any information/recommendations.

 

[BigLouie]

1. You would need to use the SOTAMAS90 DSN as a basis for a silent DSN. Use the driver for your version.

2. The TRSG will give you a good idea of which table holds what data.

Not hard to do if you know how to setup linked servers and silent DSNs. I would suggest working with your reseller to identify the tables to pull.

 

[dcrussel]

Thanks BigLouie!

 

[BigLouie]

Are you trying to warehouse the data? If so it would be better to go with a turnkey datawarehouse solution such as Datahabit.

DataHabitat offers a low maintenance data warehouse and OLAP platform for MAS90/200.

The DataHabitat out-of-the-box solution includes a comprehensive data warehouse with dozens of tables from the source system(s), about 8 pre-defined OLAP cubes, and over 300 reports covering sales, inventory, purchasing, receivables, payables, GL and CRM.

 

[dcrussel]

No, we are going to use the data as a supplement for another internal system.

thanks for your help.

 

[BigLouie]

Did you know that if you upgrade to 4.10 you can purchase the Business Objects Interface that allows you to use VB to write to the GL, AR, SO and BR modules.

 

[rainxking]

dcrussel,
I do this everyday with mas200 4.05, .net and sql.
If you have any particular questions, feel free to ask.

RK