Well, Michelle, you've presented a tough one, to be sure!

I feel that it's happening on two DIFFERENT network types is a good clue that it is *not* a "networking problem".

Being that it happens on differently-installed Win95 systems too (client did own, I assume), then something about the Win95 setup probably is eliminated too.

I'm afraid to say that it points, at least as of now, to some programming practise. Are you, perhaps, fond of certain 'powerful' commands like CLEAR (ALL/ FIELDS/ MEMORY/ PROGRAM/ READ/ RESOURCES/ WINDOWS etc)?? Maybe some variant of RELEASE??? Maybe an ill-advised UNLOCK? Possibly an inappropriate CLOSE ALL???

Whatever it is, I suggest that you NOT focus solely on "network" - it may simply be more helpful in bringing a latent problem to the surface a little more quickly.

Good Luck,
Jim N

>>Michelle,
>>
>>Maybe you should tell us more about this "network" where this seems to happen, like what make/model/version is it, running on what processor, commected to what processors/op-sys' etc.
>>
>>Most of us do network apps and do NOT have the kinds of problems you describe here from time to time.
>
>The first place it started happening was on a client's system. They are running a Novell network, but I don't know anything else about it. Since it didn't happen anywhere else, I figured there was a problem with how they had something set up. They were the only ones that had the data on a network at that time.
>
>Now we have a network set up here and are running the program. It's a bunch of Win 95 computers linked together through its built-in networking. The server is a Gateway P300, and there are 8 computers linked to it. The problem is happening here, too.
>
>That's why I think it has something to do with networks. It doesn't happen when you have a single computer running the app with the data on that same computer.
>
>This is really a major problem and I'd be extremely appreciative if someone would tell me why it's doing this.
>
>I just realized something else as I was typing. In the client's case, they're not using the server for anything but a server. Here, we use the server as a workstation. The problem is happening as well on the server. For that, the data _is_ local.
>
>I know it's not a screen refreshing problem because the trip counter gets updated just fine. It's simply not going to the next record.
>
>This might be cropping up in another place. There's a grid with the option of deleting a record. Sometimes you select delete and the record just sits there. This is new, though, so I don't know yet if this is a "lost message" problem or something I am doing wrong.
>
>Thanks,