Don't link all those tables into the report... as David indicates.

Create a blank formula for "PrintedByUser" and a value should be added runtime (assuming you have the checkbox enabled.

For Created By user (if Printed By is not good enough), we've used a script to capture that in a UDF which can be passed into the work table.

Yep, UDFs with a script to populate them in a table that can be sourced into the Wrk table  is a great way to reduce additional table joins in the report.  A lot of times you can leverage child handle objects (*_Svc classes) to get the value you need without have to get your own object handle but there are exceptions.

Kevin, I believe they are after the user who created the sales order, not the current user, which could be different if a different user is responsible for printing the picking sheets.  So BigLouie response is the best way to make sure you are getting the name of the user who created the record regardless of the current user.

Agreed, but Printed By may be enough for a process of entering then printing immediately... and it is super simple to do (checkbox and report formula).

Agreed, but Printed By may be enough for a process of entering then printing immediately... and it is super simple to do (checkbox and report formula).

Thank you both - the picking sheet was already modified by my reseller in the past. I'm a bit hesitant to unlink the tables - I'll take a closer look to see what's linked exactly and what it could be doing. I'll have to see if I'm able to figure out how to use UDFs to accomplish anything that was done with links - maybe there was a good reason?

About the user field that I'd like to add to the picking sheet, in my case it's the user who created the order, as they're often the one who needs to answer specific questions about the order the warehouse might have - unfortunately, this comes up much more than I'd like. The user who created the order isn't always the one who printed it, since the warehouse personnel print a lot of documents themselves, as well as customer service representatives.

I'll keep this suggestion in mind, as there are likely cases where I could benefit from adding the Created By user to the document.

I would make a copy of the form and try to remove all of the tables except for the work table.  Use UDFs, as someone else mentioned, to pass data from various tables to the work table.

Thanks - I'll try my best to reduce the amounts of links in the sheets. It's mostly the Sales Order, Invoice and Picking Sheet that I've worked with (and previously that our resellers might have adjusted for us in the past). 

When copying the forms, I'll simply copy them manually in Windows Explorer, right? Or, is there a more correct way to do this in Sage itself? 

What performance issues might arise from having too many links in the Picking Sheet? Would it slow down performance throughout Sage for all of the users when the picking sheet is accessed? Or, could it affect performance even when the picking sheet isn't in use?

It looks like there are two other links to other tables that were created to bring in our warehouse codes from another table, and, something else to bring in an item code. 

The best practice is using a UDF to pull the information from one table to another, then using the UDF whenever possible? Is there a limit on UDFs? In the past, maybe in the days we used MAS90, I believe I'd heard that there was some kind of character limit, which apparently lead to stinginess over UDFs...

Thanks again

I use Windows Explorer to copy forms (from a test form code / test company folder into a Live form code).

Bad report design affects printing only.

UDF limits are clearly stated on screen for each table.  I would not worry about work tables becoming overloaded, since they don't hold any data outside the printing process.

Perfect - I'd always just blown through that information without taking a closer look at it. Duh! So I'll just try to remove the links in the worksheets and replace them with UDFs that pull the information from other tables. Thanks again!