We have been for many years importing from Access Data Tables into MAS through the ODBC client for pretty much everything that goes into MAS via Visual integrator. Everything was working fine until we went to the service pack 1 update. Now the anything that uses the GL Journal Header is no longer importing correctly. The VI job recognizes the correct amount of records, but when we run a test on it and view the log it will import the first record fine then gets to the second record then it will use that same data from the second record for the rest of the records in the Access Table. When we accepted it the viewed the import it is identical as the test results. We have been working with SAGE and they seem to be clueless, they stated that they are giving this to engineering, which is a translation that we don't know what is wrong, and we are going to put this on the shelf. We import record for over 50 companies, and each company has over 3000 record to import. I desperately need this to work. All the AP and AR imports are working fine.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Importing into MAS from access problems
- Thread starter shawgod
- Start date
If it is in engineering there is nothing us poor end users can do to help. I had heard that Service Pack 1 broke the GL imports via ODBC. You other option would be to write code in Access to export the table as a text file, either ASCII or CSV and import off that file.
Here is a little trick you can do. create an Access database with your GL information and write code that is executed when the database is open. the code would create the table and then export and then close the database. You could the have VI open this database before the job so that when you run the job VI would call the Access database which would create the file and then close and then the VI job would run and import off that file!
Here is a little trick you can do. create an Access database with your GL information and write code that is executed when the database is open. the code would create the table and then export and then close the database. You could the have VI open this database before the job so that when you run the job VI would call the Access database which would create the file and then close and then the VI job would run and import off that file!
- Thread starter
- #3
- Status