>Our clients don't get these, but our QA department will, and sometimes we will see them in development. The QA area runs multiple instances often, and in development it seems that if we are running within Foxpro, after awhile this can happen if Foxpro hasn't been closed. This application is large and has a mixture of SCX/VCX and @SAY type code. Where can we begin looking (and what for) to try and eliminate these errors? Thanks!


I expected to see a reply to this thread suggesting to start using #DEFINE <g>