Pdox7 keeps crashing on Network, and phantom records 
Author Message
 Pdox7 keeps crashing on Network, and phantom records

I have an application running on a Novell network (I've tried it on
Lantastic (bletch) and Win95 (bletch bletch), and the {*filter*} keeps
locking up workstations.

The program keeps a table up on the screen with a filter running on it,
and when the user enters information into a field that affects the
filter (ie, would remove the record from view) one of two things happen:
if I use a 'forcerefresh' statement - the run-time locks up (even the
clock field freezes).  If I don't use the forcerefresh, the record below
move up one, but the rest of the table does not - giving the user the
impression that the record has been duplicated.

Help! (Please!) (Grovel)

Vaggs




Sun, 10 Oct 1999 03:00:00 GMT
 Pdox7 keeps crashing on Network, and phantom records

We are looking at purchasing Corel Professional Office with Paradox 7, we
have a Novell network.  We know little about Paradox and Access.  Is
Paradox known for crashing on a Novell Network system?  Have you solved
your problems and how?

Thanks,

Sarah



Mon, 11 Oct 1999 03:00:00 GMT
 Pdox7 keeps crashing on Network, and phantom records

Sarah: none of the common databases have a
reputation for crashing.. that's actually
a fairly silly question.. <smile>

--
Steve Green - Diamond software Group - Waldorf Maryland USA

and Corel's CTech tech support staffs but I don't represent
Borland International or Corel in any official capacity.



Tue, 12 Oct 1999 03:00:00 GMT
 Pdox7 keeps crashing on Network, and phantom records

Vaggs

One way.

Try this

Have your 'filter' fields as real fields in a mini table in :priv:

On changevalue on a filter field
Post an action to the tableframe which runs a custom method
with a TCursor or UIObject to setrange on the table
then resync(tc)  or uiobject.resync()  

HTH

Ian

Quote:
>I have an application running on a Novell network (I've tried it on
>Lantastic (bletch) and Win95 (bletch bletch), and the {*filter*} keeps
>locking up workstations.

>The program keeps a table up on the screen with a filter running on it,
>and when the user enters information into a field that affects the
>filter (ie, would remove the record from view) one of two things happen:
>if I use a 'forcerefresh' statement - the run-time locks up (even the
>clock field freezes).  If I don't use the forcerefresh, the record below
>move up one, but the rest of the table does not - giving the user the
>impression that the record has been duplicated.

>Help! (Please!) (Grovel)

>Vaggs





Mon, 18 Oct 1999 03:00:00 GMT
 
 [ 4 post ] 

 Relevant Pages 

1. Pdox7/NT4 crash choosing printer options

2. Pdox7 networking

3. Pdox7: Updating network table

4. Networked Pdox7/Win95 problems

5. Pdox7 Win95 Network Install

6. Networked PDOX7 over 64k leased line..

7. Setting Up Pdox7.0 On Network ???

8. Plug and Play Messages (95, pdox7 for 95, networks)

9. PDOX5 and PDOX7 on same network

10. Using Pdox7 tables on a network server

11. Networking PdoxWin5.0 and Pdox7.0Win95

12. Networking in Pdox7 and Pdox5


 
Powered by phpBB® Forum Software