>>>Is there a way to place my Vfp DB files in a Unix server and access them directly (Windows client) ? If not, anybody know a tool to help me?
>>
>>The DBF files can reside on whatever file server type you like; I've used the Samba client drivers successfully to access files resident on a RedHat server; you might try
http://samba.anu.edu.au/samba/>
>Ed, how would you rate reliability and performance vs NT 4? In the past, I've heard horror stories about trying to use a Win95/98 box as a file server, but NT workstation and NT server do very well. I'm considering getting one of these shoebox servers (Snap! or Linksys) and using it as a file server for some Win95/98 clients who'll be running VFP as well as VB/Jet apps. Thanks for your thoughts.
You can get away with less of a box and run RedHat Linux than run NT Server. I can get more out of a non-minimal NT Server box than I can out of an equivalent hardware Redhat server, but I know a whole lot more about how to tune and optimize NT than I do Redhat Linux. The base Linux OS on a dollar for dollar basis has more features built into it - given the usual set of base apps installed, Linux can be used to set up the minimalist small office services (file server, print server, firewall/proxy to the net, email, and small-scale web server for in-house use for administration looks an awful lot like the basic NT SBS configuration with 5-10 CALs rather than just 5-10 CAL NT Server) butr again, I can better leverage what I know, and do more in terms of deployment of extra things at the server with NT because I know more about NT.
The shoebox servers that you mention do not obviate the need for a fileserver of some sort (I assume your talking about using one of the NAS boxes) to handle the actual network administration; the places I've seen them used have still had a box running NetWare or NT Server handling network admin and licensing, with the plug&chug appliances adding more storage or a plug&play dedicated network server (I've got a client using a 3COM box that handles email/firewall/proxy duties through what servers basically as an embedded server based network hub/firewall.)
RedHat or a plug&chug is not going to do anything for you about network traffic which is what's going to hurt most VFP and VB/Jet implementations; I'd advise you to put money into cable plant (100BaseT throughout, EtherNet switch rather than a cheap hub) and not peer-to-peer where the server can get busy doing something besides server things; the more RAM available for caching, with a stable server and UPS for the whole environment, not just the server, to allow for graceful backout of workstations and servers in the event of power problems. If you anticipate lots of loading at the server, two busmastering NICs in the server and two switches will let the server carry on more simultaneous conversations.
I'd make sure that the network configuration decisions were made correctly; my endorsement of NT and a given layout doesn't help you make sure that the network gets set up right and maintained correctly. Not planning and administering the network right is likely to tunnel an installation; I'd make sure that people who know what they're doing handle the wiring of the cable plant, that there's been adequate addressing of how the network will be administered - backup is usually not planned right from the start, power protection, day-to-day routine maintenance task planning (Didn't you change the tape last night? No, I changed it last month; Joe was supposed to do it, but he's been out all last week 'cause his kids have the mumps. I guess the last real backup was made back in mid-February, but I don't know where they stuck the tape...) all needs to be addressed and planned.
Dropping the hardware in place is not the end of the install. I'd bet heavily against anyone getting the settings optimal on the first go-round. If your own network skills are not up to par, I'd contract out the network install, and even if your skills are up to par, I'd make sure that there were other resources available to handle things when you can't/won't do it, and who know enough about what's installed and how it's configured, or you can kiss off taking a vacation for the remainder of your life with the install still running. Needless to say, the client needs to be as comfortable with the other guys as with you. If you aren't local (lots of my clients are not) you need a working relationship with someone who is local (I have horror stories about what it took to find a reliable resource in the Miami area) to deal with the day to day routine and be your eyes on site when your app seems to be melthing down, to help figure out where the problem is; not being on site makes pointing a finger at you easy (it couldn't be our workstations, based on the PC du Jour Special sold to us by that hardware service kid at CompBlewUsToday, or the super-reliable Funky FileServer from Larry's Linux Lounge and Bingo Parlor down the street, or the wiring that Jim's brother-in-law Fred's cousin Mike The HandyMan put in, we know he stole the wire from the main TelCo supply site, so that cable's gotta be first rate.
It must be the Software. Since you aren't there to admire the melted mass of goo that used to be an accounting system and point the finger at the nexy gut in the circle jerk, I believe the phrase "Tag! You're it!" is often heard here.)
OBTW, where'd you put the backup tape you made when you were down 3 months ago?
