Board index » delphi » CL-Paradox on W95/W98

CL-Paradox on W95/W98

Our network consists of 3 W98's and 1 W95. Paradox behaves
unreliable on the computer with W95. Anyone familiar with this
problem ?
(Seems easy enough to solve, just change the last one to W98,
but we always seek the hard way, don't we ?)

Kees

 

Re:CL-Paradox on W95/W98


Quote
Kees Lagendijk wrote:

> Our network consists of 3 W98's and 1 W95. Paradox behaves
> unreliable on the computer with W95. Anyone familiar with this
> problem ?

Sorry, but your problem description is on the same level as "My car
behaves unreliably, could anybody tell me how to fix this situation?"
So, try again, but give some more info.

Markku Nevalainen

Re:CL-Paradox on W95/W98


OK, here are some examples:

One of our apps opens some 30 tables when it starts. Sometimes
only two tables open, on other occasions all the tables open. it even
happens that no tables open !
Sometimes the computer hangs.
Funny though, there is no pattern. I'm not looking for a solution !
I just would like to know whether someone else has experienced
these things. Specially when there is no pattern I'm feeling
like Fox Mulder...

Markku Nevalainen heeft geschreven in bericht <36992441.7...@iki.fi>...

Quote
>Kees Lagendijk wrote:

>> Our network consists of 3 W98's and 1 W95. Paradox behaves
>> unreliable on the computer with W95. Anyone familiar with this
>> problem ?

>Sorry, but your problem description is on the same level as "My car
>behaves unreliably, could anybody tell me how to fix this situation?"
>So, try again, but give some more info.

>Markku Nevalainen

Re:CL-Paradox on W95/W98


Quote
Kees Lagendijk wrote:

> OK, here are some examples:

> One of our apps opens some 30 tables when it starts. Sometimes
> only two tables open, on other occasions all the tables open. it even
> happens that no tables open !
> Sometimes the computer hangs.
> Funny though, there is no pattern. I'm not looking for a solution !
> I just would like to know whether someone else has experienced
> these things. Specially when there is no pattern I'm feeling
> like Fox Mulder...

Well, Fox, how can you see and test when tables do get open, and when
they don't get open?

I usually keep all my tables closed when the app starts, and in
FormCreate or FormShow event open only those tables that are needed.
When I Close the form, I usually also first close the tables.

If I would need to debug the Table openings, I could easily put
IDE de{*word*81} break points to all those Table.Open lines, and watch what
is there actually happening.

If I were desperate, and had to test with compiled EXE at the customer's
site, I probably would make some kind of special test Form. Put a Label
for each Table on the form, and change these captions on every Table
opening/closing. Or maybe use DataSource's OnStateChange -event to
change those test Labels. (Phew, I have newer been that desperate yet)

My greetings to Scully:)

Markku Nevalainen

Re:CL-Paradox on W95/W98


Quote

>Well, Fox, how can you see and test when tables do get open, and when
>they don't get open?

>I usually keep all my tables closed when the app starts, and in
>FormCreate or FormShow event open only those tables that are needed.
>When I Close the form, I usually also first close the tables.

too messy for me. I open all the tables at startup. To give the user
something to look at I've made a progress-bar which move along every time
a new object is created/opened. Something like (discard the syntax):

DataModule1.create;
Log('DataModule1 was created'); --> is written to log-table
Bar.stepit;
DataModule2.create;
Log('DataModule2 was created');
Bar.stepit;
Table1.open;
Log('Table1 opened');
Bar.stepit;
etc.

This way you can forget about opening tables during execution

But sometimes the Win95-machine hangs between steps (and
not always at the same spot) ?

Kees

Re:CL-Paradox on W95/W98


Kees,

What exactly does 'Paradox behaves unreliable' mean? You're not
giving any information we can use to help...

Ken
--
Ken White

Clipper Functions for Delphi
http://members.aol.com/clipfunc

Quote
Kees Lagendijk wrote:

> Our network consists of 3 W98's and 1 W95. Paradox behaves
> unreliable on the computer with W95. Anyone familiar with this
> problem ?
> (Seems easy enough to solve, just change the last one to W98,
> but we always seek the hard way, don't we ?)

> Kees

Re:CL-Paradox on W95/W98


Ken White heeft geschreven in bericht <369A85C1.88B34...@westelcom.com>...

Quote
>Kees,

>What exactly does 'Paradox behaves unreliable' mean? You're not
>giving any information we can use to help...

>Ken

Ken,
thank you for replying. However, if you do not know
what I'm talking about you probably won't be able
to give me any suggestions.
Anyway, I'm not really looking for solutions. I simply
want to hear someone telling me that I'm not the only
with unreliable Paradox-tables...

Kees

Quote
>--
>Ken White

Re:CL-Paradox on W95/W98


Quote
Kees Lagendijk wrote:

> Anyway, I'm not really looking for solutions. I simply
> want to hear someone telling me that I'm not the only
> with unreliable Paradox-tables...

If that's all you need, and it will solve something in your case, try
make a couple of DejaNews searchs, http://www.dejanews.com/home_ps.shtmlsearch

You should find postings saying "I have problems with Paradox...Heeeelp me".
And also those who say they have built multi user apps, having hundreds of
megabytes BDE/Paradox tables with no significant problems.

Markku Nevalainen

Re:CL-Paradox on W95/W98


Quote
Kees Lagendijk wrote in message <77dib3$hf...@reader2.wxs.nl>...
>OK, here are some examples:

>One of our apps opens some 30 tables when it starts. Sometimes
>only two tables open, on other occasions all the tables open. it even
>happens that no tables open !

Kees, make sure that Session.KeepConnections is set to false, also check BDE
config MaxFiles setting...is the IDAPI.cfg file centralized or local to each
workstation ? if it is localized, compare setting to w98 machine.

I had a small table repair utility that scanned multiple directories for
db's to checkout, and until KeepConnections was set false, 25 was the most
tables that would open!! (in other words, if all your tables are in the same
dir, this may not help).

BTW: make sure that your tables are not in the same dir as your app!

Later
Frank

Re:CL-Paradox on W95/W98


Kees,

Quote
Kees Lagendijk wrote:

> Ken,
> thank you for replying. However, if you do not know
> what I'm talking about you probably won't be able
> to give me any suggestions.
> Anyway, I'm not really looking for solutions. I simply
> want to hear someone telling me that I'm not the only
> with unreliable Paradox-tables...

Your question is like saying to your mechanic "My car isn't working.
How long to fix it and how much will it cost?".

You haven't provided any information with which to even consider
coming up with an answer. And I've been working with Delphi since
1.0 was initially released; your comment about my not being able
to give suggestions is rude.

If you want to actually provide a question with at least basic
information, I'll be glad to try and help. If you want to continue
being vague and rude, I withdraw the offer.

Ken
--
Ken White

Clipper Functions for Delphi
http://members.aol.com/clipfunc

Other Threads