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

Hi Bruce, That's really helpful. I'd clearly been looking at that in the development of my pivottable but had forgotten about the extra tables seen there. I put it down to advancing years. I must have twigged that a number of tables don't actually feature in the output of the PJACT.report and ...

Hi Bruce,

Eeek! By my count that report has 18 tables (although I'm not sure what to make of the top right table which doesn't appear to have any fields).

Do you mind me asking what report that screenshot is from?

Kind regards,

Ian

Hi, Having done this for a pivottable report recently, I think the columns you'll need are: PROJECT.CUSTOMER_REF, SALES_LEDGER.NAME, PROJECT.REFERENCE, PROJECT.NAME, PROJECT_TRAN.PROJECT_TRAN_ID, PROJECT_TRAN.AUDIT_TRAIL_ID, STOCK_TRAN.TYPE, PROJECT_ONLY_TRAN.TYPE, AUDIT_SPLIT.TYPE, PROJECT_TRAN ...

Hi Ian, I feel your pain. While you wait for a fix, maybe play around with the background image? If you remove it does the problem go away? It's likely that you wouldn't have paid much attention to the file size in 2016 if it just worked without issue back the. Maybe there would be a smaller file ...

You're welcome.

Hi Steve, Checked and I think this should work. Sheet1!$E:$E,"=40??" Regards, Ian PS Whilst this happens to work for your specific circumstance I'd be inclined to convert the code to a number, either in your query or in your worksheet, and then base the SUMIFS on the numeric version of the code ...

Hi Steve,

Could it be a text v number thing? As I understand it the Sage nominal code field is of type VARCHAR.

brucedenney wrote: ↑12 Feb 2021, 12:15 I think you use Excel and it is compatible.

Phew! Many thanks.

Hi Bruce, It's just a little concerning when our product line relies on the reliable operation of the ODBC drivers! Maybe we are geniuses at SQL (without knowing it) or lucky that we haven't had any issues? I know it's a bit off topic (and a bit cheeky on my part - sorry) but I'm intrigued by what ...

SomeGuy wrote: ↑11 Feb 2021, 07:43
I was reading a post on Sage's own support forum the other day where they were saying that they don't even support reading via the ODBC driver ...

Eeek!!

Hi Someguy, Very interesting. I've played around a bit and it seems that the MS Query interface does indeed have a 255 field limit. However the ODBC driver does not. What I've done is use MS Query to set things up with a single field query like SELECT STOCK_CODE from STOCK and then edit the SQL in ...

Onion Reporting Software aims to provide simple to use, low cost, yet flexible, high added value reporting products to the small business community. With many years of experience of working with financial reporting software for large businesses, responding to users’ needs regarding robust visibility ...