>Can you be a little more specific about the bugs you've seen? Are running 3.0b? I ran 3.0b apps on NT, Novell, and Banyan Vines (ick) networks successfully (if somewhat slowly!).
>

There were several annoying things about 3.0, mostly related to the incomplete support for UNCs, and problems accessing some APIs that I rely on to map and disconnect map drives.

>>Most of the recent bugs we've come up with have been related to Networks. Can anyone help me with what the most common VFP3 bugs on the networks are AND whether it would be a bad idea for a client of ours to move the application to the Novell Netware 5.0 (he's currently on 3.12)?

My opinon (and this is definitely an opinion not shared by everyone) is that there are a tremendous number of problems related to NetWare 4.x and Client32 which have not been resolved completely. I don't have any detailed experience with 5.0, other than to note that not all the problems clients were reporting with NetWare 4.x and later releases of CLient32 are gone. I've had better success with Microsoft's Client for NetWare, but it's slower than Client32 in many circumstances. It's also a less pretty interface.

If your client is not in need of NDS, I'd strongly consider going to NetWare 3.20, which retains the features and interfaces of 3.12, but adds Y2K compliance and a ton of patches. We had several reasons to do this; we don't use NDS in-house with only 2 NetWare servers and an NT Server in the production environment, so the single most compelling thing about NW5 wasn't a factor, and we have a significant investment in software like CA-ArcServe that we would have needed to upgrade at the same time.

We went to 3.20; it had no effect on our workstation configurations, batch files, scheduled jobs and the like. We did not have to reformat and reinstall the servers; the 3.20 upgrade applied to the 3.12 systems without altering the basic disk loayout. It's our intention to eventually phase out NetWare entirely, transitioning to NT Server instead since we rely on things like Exchange Server, and will more than likely be putting up SQL Server 7 in production within 6-9 months.

YMMV.