Hi This is the second office that has brought up the issue of Rbase getting slower as the day wears on.
This tech is a certified network guy so I assume the network is OK, new computers 1 gig switches ... 2. We have an issue where the "client" unit is apparently having a memory or other issue. I'm going to run a perfmon log against it tomorrow to see if it looks like a memory leak. Basically, by noon, the client PinnSoft is running extremely slow. A shut down and restart of PinnSoft (not the computer) resolved the issue, but it gets worse again. I've tried removing all AV and other related security products and it helped a little, but didn't resolve the problem. I'll let you know what we find. Any suggestions? I am trying to find out if all parts of my app get slow or just some of them. The other office said this EEP would get slow My old code used a regular table and I would just delete rows ..... -- tran_spd is a temp table that is created on start of the main menu DELETE ROWS FROM tran_spd -- APPEND speedov TO tran_spd WHERE custnum = .vcust -- xx RUN transpd IN prog7.apx INSERT + INTO tran_spd (custnum,date_con,tr_date,tr_type,ch_code,ch_price,+ ptest,dig_ch,memo,treat_dr,inscomp,inshold,modf1,modf2,modf3,+ modf4 ) SELECT custnum,date_con,tr_date,tr_type,ch_code,ch_price,+ ptest, dig_ch,memo,treat_dr,inscomp,inshold,modf1,modf2,modf3,+ modf4 FROM speedov WHERE custnum = .vaptcust EDIT USING spdyov2 + WHERE tr_type = 1 AND custnum = .vcust CAPTION .vcap They click a button to Save or append these charges to another table then go back to this same EEP again. Could the old deleted rows that are still around in the Temp table be doing this? Would a packing the temp table help? Marc
