>Has anyone distributed a VFP8 app and ran it on client workstations with celeron chips, Windows XP home, and 128-256mb ram with no problems?
Only on PIII-based Celerons (up to 1200 MHz).
We did some rudimentary checks with processors in 2000 and 2002.
For deployment:
The PIII based Celerons were quite comparable to PIII with 10 to 15% less frequency.
The PIV based Celerons (Northwood/130 Nm Core) were much worse compared to PIV's, and strongly "not recommended" but workable. Frequency Hit 25 to 35% - not cost effective.
AMD Tunderbird, Duron and XP: all workable, Performance slightly above the PIII of comparable speed (Duron vs. PIII Celeron)

For development:
A huge speed gain can be observed if you have large include files called in most classes and large processor cache. Therefore the smaller CPU's (Celeron/Duron) are NOT recommended.

On the new Prescott core:
we haven't done any analysis yet, but believe the performance hit for the celeron compared to the PIV is less extreme, since both CPU got their caches doubled. This should help the Celeron relatively measured more. Still, it is drawing too much power IMHO and not a good buy overall.

Memory: we ran NT/W2K with a minimum of 160 MB. Since I guess your clients are still in insurance it is my guess that the basic memory needed for booting in the installed OS is at least 100 MB.
For XP anything under 256 can create problems IMHO, and if there are also problems with the disk (UDMA not working/switched off, disk too full or fragmented, slow laptopdisk only?) hiccups should definitely be expected.

>We have some Pentium III systems running fine but the celeron systems do appear to become sluggish by the end of the day... Ideas???
Sounds like the disk is working too much at the end of day... Memory leakage ? Reboot helps or defrag during nighttime ? Temp File filled up, which automatically gets cleaned on reboot ? Or is a defrag scheduled for a certain time ? (had that one: at 12:00 sharp everybody was supposed to take their lunchbreak...)

HTH

thomas