On a current-version Windows machine where this problem never occurred
before, the "File..Open..Table" dialog box (Paradox 10) now refuses to list
anything for ODBC data-sources and immediately reverts back to the previous
alias-name.

This problem has been talked-about before, saying that "Windows-XP service
pack thus-and-so" introduced it, but this can't be the case here because
it's "Server 2003 SP1" and, as I said, the problem recently /appeared/ ...
one user, it would seem, at a time.



----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep

Sundial Services wrote:
Also... a script that opens the alias and requests a list of tables
therefrom has no difficulty whatsoever in doing so. Lists only about 90
tables. The number of tables, names, etc. has not changed in a long time.


----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep

2003 server IS xp, isn't it?

And if I recall, this is ONLY interactive; OPAL doesn't have the problem.


--

Tony McGuire
"It's not about having enough time. It's about priorities."
___________________________

Tony McGuire wrote:
Hard to say. But it certainly wouldn't "crop up." And it wouldn't "drop,
user by user."

There is obviously /something/ that is generating some kind of runtime-error
early in the processing sequence for _any_ ODBC data-source.

----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep

Tony McGuire wrote:
A script has no difficulty in connecting to the alias, obtaining a list of
tables, or anything else.

----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep

Exactly. OPAL doesn't have the problem.

'Interactive' means the user going thru the steps to access the database[list]
with a mouse or keyboard.


Are the workstations winXP?

MIGHT they have automatic updates on, and they have been updating to sp2 ONE BY
ONE?


--

Tony McGuire
"It's not about having enough time. It's about priorities."
___________________________

Tony McGuire wrote:
Nope. Nope.

----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep

I am not sure I follow what you are saying,
by 'one user' at a time,
do you mean multiple users on same machine ?
or do you mean different machines ?

Is the problem intermittent on the same machine ?
On monday, interactive does not work,
but on tuesday it does,
and weds it does not ?

Do all the machines that you are talking about
have Server 2003 as their operating system and not Win XP ?

The description of your symptoms,
is the same symptoms that I get
using Pdox 10 on Win Xp with the service packets.

Maybe a specific dll gets overwritten ?
Maybe the appcompat program from msoft could be used....who knows.

Interesting.....and it will be interesting if enough people brain storm this
so that
we could collectively find the fix for pdox 10 without having to purchase
Office X3.


Robert Wiltshire

Robert Wiltshire wrote:
Do we have a solution in Pdox 11?

----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep

Yes. SP3 fixed this.

--
Bertil Isberg - CTECH
Paradox buglist:
online: http://web.comhem.se/~u82608896/

"Sundial Services" <info (AT) sundialservices (DOT) com> skrev i meddelandet
news:440f574e (AT) pnews (DOT) thedbcommunity.com...