If you're concerned about deleting the Foxuser table, then rename it. YMMV, but in the past years of helping people resolve C5 errors, my experience is that getting rid of the Foxuser table seems to be the thing that most often fixes the problem.
>Hi Craig,
>
>is that a good suggestion? Maybe the third or fourth thing to try, but not the first. Remember, many people have a lot of settings stored in their foxuser table. I have had several c5 crashes over the years, but none of them was caused by the foxuser table, it was always a bad driver or a bad ActiveX control or something like that.
>
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer