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

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 ...

If you have an error or more then the problem is almost certainly the data error. The way the sage database works is as a linked list, each transaction points to the previous and the next. When you get errors it is normally one of these that has broken. Data repairs work by going through the ...

Delete the user and recreate

You do not want to be using a sub report. The problem you have is that it is adding up the Qty_Order for all the lines in the details section (where the BOM is printed) You only want to add it up when the Sop_Item changes. To do this select the QTY_ORDER expression in the Page footer (I would ...

You do not want to use a sub report.

Just to be clear you want the total quantity of items on the order (excluding BOM components).

Please attach your report so we can see what you have done.

Looks like that c:\skyewright path is the server path and it is a classic install.

Do a classic install to that directory and it should be good.

You have updated a workstation without updating the server first or have install as a standard install when it is server install, or possibly you might have a classic install.

What directories are under c:\skyewright?

Here are the instructions.

https://www.makingithappen.co.uk/CI/upgrade.htm

You will need to delete the revalued invoices/Credits then re-enter them and rematch them but on the correct date.

Deleting the revalued transaction also deletes the revaluation transaction.

This is what I use in Office VBA to build the string ConnectionString = "ODBC;DSN=SageLine50v" & DN & ";UID=" & UR & ";PWD=" & PW & ";DIR=" & DR & ";" DN is the Sage version UR is the UserName PW is the Password DR is the path to the data folder including ACCDATA at the end.

I think you would need to redate the reval transaction by editing the transaction.

The solution is to match the transactions on the same date, then you don't get the revaluation happening on a different date.