General Consultant Discussion

Somewhat related to Sage 100. We use Access databases to query and report when only Access will do. We have a job profitability report one client lives and dies from. This morning, this single page per job report margins are whacky and it's bleeding onto four pages. If we preview, change the margins back to .25"" on all four sides, all is well. Problem is, it's not holding the settings. It sounds environmental to me. Ideas?

Check the default printer or page size on the client.

Are you using Crystal reports from with Sage to hook into your Access PTQ tables?

I use an rdp connection and the default printer is my local printer (redirected). The margins are not sticking if I change them in Access print preview. I'm asking local users who complained this morning to check this now. I'm printing an Access Report, not Crystal. Actually, this is an Access Frontend to SQL Server. We use a linked server to Sage 100 to get the data.

Interesting. Can't wait for @PhilMcIntosh MOTM Session on this topic (linking Sage 100 to a SQL database).

Runs lickity split if you create the queries in SQL. Don't bother doing them in Access unless you're running against small files or SQL tables. An update process that previously took 20-25 minutes in native Access now takes around 2 minutes. Given the huge number of transactions we are parsing and summarizing, this is awesome.

OK. Here's how we resolved the problem. Turns out you have to be very careful how you set printers and margins in an Access database that you intend to compile. The settings are not changeable in the accde compiled versions. Once we corrected the settings in the developer database and compiled, we were good to go.

Cool, thanks @KathrynScofield for closing the loop.