Strange errors with :priv: report master table

Hi everybody!

I'm using either the ReportPrintInfo.masterTable property or the corresponding DynArray element to set the master table of a report just before printing it with report.print.

What happens is that if I generate a QBE query with all the conditions I need and pass it as masterTable to the report, all seems to work properly, but if I tell to the very same QBE to produce a temporary table in :PRIV:, and then pass that table to the report as a master table, the report shows many strange errors, refusing to run telling that it has no table, missing fields, any time something different that makes it crash, and sometimes also makes PDX crash.

Note that the table is being created correctly all the times: if I step debug my code and stop after executing the QBE, the table is there sitting in :PRIV: and has both the correct structure and the correct records inside, so why is it complaining that the table is missing or that fields are missing?

I vaguely rememeber something about Liz saying there was a max length of the PRIV path, but I can't find anything online about it...

Also, I hoped that all these path problems where a thing of the past since I started using an AutoIt startup script to SUBST drives to relevant folders, so that my aliase's paths turned to something very short such as:

c:\Users\User\Atipica\Alatron\Prv => y:\Alatron\Prv => :PRIV:

And similar things for all the other aliases.

I'm baffled, since nothing seems to resolve this apart from using directly the query, wich is perfect 90% of the times, but sometimes some calculations that cannot be performed on a live query should be applied to the created table, and in these cases I'd like to use the table...

What I'm missing here? Any hints?

Thanks!

Frelance IT consultant and programmer since 1991: www.atipica.it

keep the path under 32, and keep the printer names under 32, too.. Win10 likes to re-install printers with names as long as your arm

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN

Ok, I'll check the printer name and the path length, what do you think about my idea of using substed drives to shorten the paths, do you think it helps or not?

Thanks!

Frelance IT consultant and programmer since 1991: www.atipica.it

if the path name is too long, doesn't matter which way you shorten it.. the printer name, you are best to actually be a shared printer, and shorten the network name

Steven Green
Senior Software Engineer
Paradox Support Specialist DOS/WIN