Here is an extract from this case study.
Lawson users must still be recovering from the holiday I guess!
As Steve's post indicates one would expect to be able to extract the data from printed output - a basic list of ledger transactions might be enough for example - or maybe even by ODBC/OleDB/Etc. link directly into the database if such access is allowed and available and you have a Pro version of Monarch.
Is there some other aspect of your requirement (and hoped for responses) that we have not spotted in the original question?
We are aware that we can Monarch any report generated from Lawson but we are more interested in knowing if we can link directly into the database by the ODBC/OleDB/Etc that would allow us to report at any time, without the constraints of just when a report is generated. We do have the Pro version so I am thinking that we can, and if so would anyone have any knowledge how to set it up against the database. Any information would be appreciated.
While I don't have first-hand experience with connecting to Lawson databases, it [URL="http://www.clackesd.k12.or.us/nis/lawson/docs/AccessingLawsonDatawithExcel.pdf"]seems like it is possible[/URL].
We are aware that we can Monarch any report generated from Lawson but we are more interested in knowing if we can link directly into the database by the ODBC/OleDB/Etc that would allow us to report at any time, without the constraints of just when a report is generated. We do have the Pro version so I am thinking that we can, and if so would anyone have any knowledge how to set it up against the database. Any information would be appreciated.[/quote]
Do you have any other reporting tools already accessing you Lawson system? If so there may already be an ODBC/OleDB type definition available that you can call up when you define the connection.
If not ... it depends on how the data is stored.
The task will be slightly different if it is a 'database' product (which will likely have a definition built in) or in flat files (older systems.)
(If you have flat files you need to get the information about the data structure. )
The document Kruncher referenced outlines the process although of course the specific files/fields/servers and so on will be different for your purposes.
At the Monarch workface just go for the 'Open (a) Database' option and then follow the wizard down the ODBC options path. That will list all the links available to you.
Some thoughts though.
Ledgers tend to have a lot of entries. Depending on how the indexes are set up compared to your enquiry purposes (and network traffic and so on ...) retrieval may not be fast.
If you are not selecting on a 'frozen' period you may have some inconsistencies in the selections made for each enquiry/refresh.
If you work interactively with the database you may need sole access - somewhat constraining when things might be available to you OR the rest of the system might be available to other users! You are also hitting the server - possibly quite heavily - as often as you interact with it.
If you can work with a system extract you don't hit the server, you won't have the potential of changes being recorded as you work and any sole access requirements will, of course, be eliminated.
I fully endorse both methods of access to the data but it is worth being aware of some potential issues (they may not apply as described) when you start out!
I would guess you have someone performing a Database Administrator role for you. They are probably a good source of information.