Access Lawson tables in MS Access

I believe you need to install the OLEDB Query Builder as well as Excel Add-Ins for Lawson, which can be downloaded from the support site.

Sorry if I'm raining on your idea, but this sounds like a bad idea. It's not dynamic (i.e. you would use the query wizard into Excel, save as .xls, then connect Access via ODBC up to it?)

I don't have enough information on the poster's environment/goals/limitations to determine whether it's a "bad idea" or not. The poster wanted to know how to bring data into Access via OLEDB, and I am presenting a possible way to do this from a technical perspective. Would I pursue this as a solution for myself? Absolutely not. I try to avoid Access at all costs due to its limitations (ie scalability, etc), and as you suggest the solution presented is not dynamic.

I built an access program to decipher all of the APAUDIT codes.  It is in the Source Exchange over at lgug.net.  I ended up combining 3 different sets of definitions from 3 different sources to get what I felt was a pretty accurate listing.

John, It's not raining here. Perhaps a bad example. With Access I can tie data together from Lawson HR, GL, & AP & Credit Card provder SBF, CIF, etc files, and separate travel program database to create all kinds of requested reports and analysis. This can also be done in Crystal Reports, however developing analysis via Access is generally much faster due to the 11x17 limitation. Someone made a comment about scalability and cost. My work experience is dealing in the 100's to 200,000 records range. Occasionally in the 600,000 range but that's it. Even with Access 2002 and older ODBC drivers it rips. My major observation is not the volume of records, its the combination of working with Tables I regularly update with downloads from the travel agents website, the card providers website, where field properties can be changed easily in Access inorder to make joins with Lawson or other non-Lawson Tables. Building a report from several data sources which execute at the click of the run button is a lot more efficeint than getting disjointed data in Excel and playing with manipulating strings and numbers to use with multiple vlookups.