Actually I was using ODBC before until the PO2 gets too big (more than 50K records) and takes more than 5 hours to export. Then I tried VI export which is a little faster, but still too slow. And RM takes less than a minute ! My guess is the PO2 and SO2 are indexed only files (not keyed), so the ODBC driver is not very efficient in dealing with them.
I am not extremely familiar with RM, but here is a command line I use for VI to import. It may apply.
M:
CD\
CD MAS90\HOME
M:\MAS90\HOME\PVXWIN32.EXE ..\launcher\sota.ini ..\soa\mas90 -ARG VIWI0V W O DIRECT DISPLAY DTC
This all being in a batch file I call.
Regarding ODBC, if You are using PO2 and SO2, maybe checking for receipt dates for sales order lines, consider if using access using a make table on PO2, then a seperate one on SO2, then base your query on the local copies of both of them. The make with no joins runs much quicker.
Hope that helps you,
ChaZ
There Are 10 Types Of People In The world:
Those That Understand BINARY And Those That Don’t.
I've tried the VI command line and it doesn't seem to work. So I think I will try export PO1 and PO2 separately and do something outside and link them up. Thanks for the advice.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.