[AccessD] A2000: Am I blind? (swe)

Charlotte,

Now, now, you're talking to someone who took a long time to be weaned
away from Paradox. It's like giving a sniff of whiskey to an
alcoholic, you understand? There are things that can be done with the
default report designer in Paradox for Windows that cannot be done in
Access -- e.g., nesting continuous subreports inside a continuous
subreport inside a continuous subreport. I miss that.

And, regarding not being able to bind a query to a report, you're
right. I was very happy to see that capability in Access.

Not sure what you mean by Paradox queries defaulting to totals
queries. It defaults to a SELECT DISTINCT MakeTable query, that I
know. But "totals" queries by default? Can't picture what you mean.

But it's all so academic now that Corel has stopped all development on
Paradox. My list of Access vs. Paradox had quite a lot more on the
Access side of the ledger by the time I gave it up.

Steve Erbach


On Mon, 14 Feb 2005 08:51:40 -0800, Charlotte Foust
<cfoust at infostatsystems.com> wrote:
> Hah!  In early Paradox for Windows, circa Access 2.0, you couldn't even
> bind forms and reports to queries, all you could do was display them.
> How's that for funtionality? <g>  And Paradox queries were totals
> queries by default.  That could really confuse someone who changed the
> order of fields in the query and got a totally different result.  I
> supported our sole Paradox dabbler some jobs back because I programmed
> Access and could understand what was going on ... Or going wrong in
> Paradox.
> 
> Charlotte Foust