Win95 fileserver & Paradox locking problems? 
Author Message
 Win95 fileserver & Paradox locking problems?
I have heard that Paradox for Windows will not lock records properly when
run against data on a windows 95 file server - that it is possible for one
user to edit a record that another user has locked.

Is this true? I am thinking of reccommending this setup to someone.

Is anyone using a Windows 95 machine as their fileserver with Paradox for
Windows?  How is it going?

Thanks

-Greg



Tue, 30 Jun 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?

: I have heard that Paradox for Windows will not lock records properly when
: run against data on a windows 95 file server - that it is possible for one
: user to edit a record that another user has locked.

I think this crops up when you mix 5.0 and 7.0 using win 95's peer to peer.
Apparently the peer to peer networking is too slow to get the record lock
over there before someone else can possibly lock it.

: Is anyone using a Windows 95 machine as their fileserver with Paradox for
: Windows?  How is it going?

Although it probably could be done, I'd recommend a more robust file
server, such as NT Server or Novell's Netware over Win'95 as a file
server any day.

Andrew
--
Andrew Bennett



Wed, 01 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?

Quote:

> I have heard that Paradox for Windows will not lock records properly when
> run against data on a windows 95 file server - that it is possible for one
> user to edit a record that another user has locked.

> Is this true? I am thinking of reccommending this setup to someone.

> Is anyone using a Windows 95 machine as their fileserver with Paradox for
> Windows?  How is it going?

> Thanks

> -Greg


I have run into this bug. Evidently Win95 peer to peer has trouble
locking the record. I switched over to all PDOX 7.0 and Win95 and
have not seen a problem since.

Dosn't say much for Borlands claim of backward compatability does it.



Sat, 04 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?
I have a Windows 95 File Server with WFW 3.11. We seem to be working OK on locking of files,
although I am by no means a network expert. The part that REALLY bothers me is that if the
server goes offline, I get a SYSTEM ERROR-can not read Drive I: White window comes up on any of
the machines that were using the fileserver, and even AFTER the server is rebooted and
available, the Buttons RETRY and CANCEL dont work, meaning after we get the above system error
message , that window says retry or cancel, and hitting retry 1000 times will not get you
reconnected, even if the server is available, and cancel will not cancel the window either, it
seems to be stuck in a loop. This problem is not specific to win 95, i had the exact same
problem with a peer-to-peer network with WFW 3.11. I tried the same setup for 2 win 95
machiens, same result. Why cant PAradox reestablish communications??? You figure this out I
will be ecstatic......Dwight Furleigh Caterpillar Ag products


Sun, 05 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?

Quote:


>: I have heard that Paradox for Windows will not lock records properly when
>: run against data on a windows 95 file server - that it is possible for one
>: user to edit a record that another user has locked.
>I think this crops up when you mix 5.0 and 7.0 using win 95's peer to peer.

This may have been the situation it which the problem showed up. I will
check back with my source.

Quote:
>Apparently the peer to peer networking is too slow to get the record lock
>over there before someone else can possibly lock it.

That would surprise me if the speed of the network was the problem. In my
non-scientific tests I did a few months ago when I installed NT at my
workplace, I found that a win95 to win95 network connection was the fastest
thing I'd ever seen! I was really blown away. Now, I think I heard that you
can only connect 10 computers to a win95 server, and I don't know it the
performance scales well, but it was noticeably faster than the NT server!
Perhaps the problem is with the implementation of the networking rather than
the speed.

Quote:
>: Is anyone using a Windows 95 machine as their fileserver with Paradox for
>: Windows?  How is it going?
>Although it probably could be done, I'd recommend a more robust file
>server, such as NT Server or Novell's Netware over Win'95 as a file
>server any day.

Yes, I agree, but the people who will be doing this only hae 4 computers
now, and an NT server seems like overkill - especially cost-wise. But, I
guess an NT server wouldn't have to be dedicated either.

Thanks for taking the time to answer my question!

-Greg



Sun, 05 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?

: >>: I have heard that Paradox for Windows will not lock records properly when
: >>: run against data on a windows 95 file server - that it is possible for one
: >>: user to edit a record that another user has locked.

: I have since heard that the problem is fixed by one of the three patches to
: windows 95 available from the Microsoft Web Site.

Any information regarding what the name of this patch is would be
appreciated, as I'm sure it'll be a FAQ for some time...

Andrew
--
Andrew Bennett



Mon, 06 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?

Quote:



>>: I have heard that Paradox for Windows will not lock records properly when
>>: run against data on a windows 95 file server - that it is possible for one
>>: user to edit a record that another user has locked.

I have since heard that the problem is fixed by one of the three patches to
windows 95 available from the Microsoft Web Site.

-Greg



Mon, 06 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?
As I understand it:  Pdox for Win 5.0 uses a locking resource that is no
longer available in Win 95.  

Thank Microsoft for changing that and Borland for not seeing it coming
or informing its user base.  

Pdox 7.0 uses the more Microsoft standard locking resource.  That is why
your problems disappeared by using 7.0.  My experience says don't use
5.0 on a Win 95 network.  You will have corrupt tables.

Running 7.0 on a Win 95 Net is fine.  One respondent said that he has
5.0 on his Win 95 file server.  That is OK if all workstations are
running 7.0 and the file server just delivers data.  That means that 5.0
isn't even involved so there is no locking problem.

Hope this helps.



Sun, 12 Jul 1998 03:00:00 GMT
 Win95 fileserver & Paradox locking problems?
I have a customer who is using pdx 5.0 on each workstation and also
on the server.  All those pc`s are using win95. It was used to have
corrupted tables when the server (win95) was setup as File Server (in
control panel | system | performance or troubleshouting tab).  As
soon as we put it as "Descktop computer", they never got corrupted
tables again.

!!!

Fran?ois Gaucher



Sat, 18 Jul 1998 03:00:00 GMT
 
 [ 9 post ] 

 Relevant Pages 

1. Paradox locking problem with Win95 ??

2. Problem with Paradox 4.5 Application with NT4 Workstation Fileserver

3. Paradox locking under Win95

4. Win95 - Paradox DB - Record Locking Bug?

5. locking in paradox 4.0 under Win95

6. Paradox locking under Win95

7. !!!Urgent!!!! Paradox Databases on Fileserver without Clien/Server

8. Conflict between Paradox 4.0 & Win95

9. Paradox 4.x & WIN95 Novell -

10. Paradox 4.5 (DOS) & Win95

11. ODBC16 & PARADOX 7 (win95)

12. Please help: Delayed Updates with Paradox & Win95


 
Powered by phpBB® Forum Software