SageForum for UK versions of Sage 50- Help and support.

The date on the purchase order is an 2 places.

There is one on the order and then multiple ones for each item.

Which you use depends on when the goods will be delivered. The whole order or in parts.

Note there are DUE_DATE and an DELIVERY_DATE which are easy to confuse.

You could work out the lead times by looking for GI transactions in Stock_Tran and comparing the date they were received to the date they were ordered on the PO. Not sure what you would then do with that. If you are building a model of stock requirements then, that is very dependant on the business ...

You can't convert reports, they refer to different variables in different tables.

You can use templates to apply a look and feel to all reports.

Please attach the SageDB dsn

Put a page break after on the invoice footer section.

You need to add a section for the invoice number so it can split, see this.

There are a number of things that can cause this.

Do some file maintenance. A reindex and compress and see if that helps.

The stock transfer is set up using a BOM Create your sample product code, go to the BOM tab and enter the recipe to make it, add the source product and in the Qty enter 0.1 if you get 10 samples or 0.833 if you get 12. Once setup, you can do a stock transfer enter the product you want to make and ...

So just select grey and the job is done.

No You can use all the attributes exposed eg suppress print. Background colour is one of the options, not sure what your issue is? I thought you were wanting a border setting. ive guessed the synatx to add the border colour condition: The way to do that is to draw a box around the item set it as ...

The border is not an option.

The available options are shown in the wizard.
However, you could add a text box around the subject and then suppress printing with a conditional format to get the result you are looking for.

I don't use the SDK it is expensive, I use a 3rd party tool to write my integrations for others. The ODBC drivers are slow, they use a comma as a separator or something like that, which makes some SQL ambiguous. It is what the report designer uses and is functional for many if not most purposes. You ...

Your mileage may vary.

It depends on what you are doing, how big the database is and so on.

You should try it an see.

ODBC is slow.

Hi Decimal places can not be set from a conditional format, however... You can create 2 fields one with 2 decimal places and one with none, you can then set one to be suppressed from printing. You then use conditional formatting to make the supressed on print if there is a match with the desired ...

The sage report designer, extracts data form sage using the ODBC drivers, so performance should be comparable. The drivers are slow. What you do with PowerQuery may be complex and slow things down even more. A popular solution, where data does not have to be up to the moment, is to cache the data in ...