>Real strange issue:
>
>Client has our app. installed on a network, NT, workstations WIN98 first edition.
>
>The use a particular section in our app. all day, then every so often when they go into the same section they have been working on most of the day, one of the grids appears blank (table not associated, closed, whatever.. I can handle that).
>NOW COMES THE WEIRD PART...
>When this happens, (blank grid), the user has to reboot the workstation. If they just log out of the application and try resign on, the error continues. It only disappears when the user reboots the workstation. Not the server, the workstation.
>
>Anyone have any ideas.

SWAG, bit it sounds remarkably close to a problem we had with a hybrid Win2K server, and a station that, after sitting idle for a period of time, would blank a grid, and would actually lose connectivity to the drive letter mapped to the remote resource. Rebooting, which forced a complete disconnect/reconnect, or using WNetCancelConnection2() to drop the drive letter mapping, followed by a call to WNetAddConnection2() to recreate the mapping, cleared the problem. It turned out that we had exceeded a threshhold on the Win2K server hosting the connection, so that if a connection remained idle for a period of time (somewhere in the 15-30 minute range) it would discard the connection at the server in order to free up an apparently idle connection; Win98 was dain-bread and was unaware of the server-side disconnect, and assumed a connectivity error occurred, and rather than reestablishing the connection to the idle mapped drive, it invalidated the mapping and refused to reconnect, because WNetCancelConection() had never been called to release the drive mapping, so a subsequent attempt to remap the drive failed because the drive letter 'slot' was still occupied. After proving out the behavior, we adjusted the behavior of the Server service under Win2K server to allow an infinite number of connections before recycling idle mappings:

           Key: HKLM\System\CCS\Services\LanmanServer\Parameters
Key Value Name: CachedOpenLimit
Value Assigned: DWORD:0x0

I don't know the equivalent registry hack for NT4, but you might try www.ntfaq.com