Hi all,

I've currently got a few xlookup commands on form entry to grab values from another database.  So, when I hit F10 to go to the next record, it takes 1-2 seconds.  No big deal.

However, when I run a mass update, it looks like it runs these form entry commands, so a mass update of 10,000 records will take *forever*.

What sort of condition can I place on my form entry code so it doesn't run when I do a mass update?

Or do I have to copy my form to another form, and take out the form entry programming, to have a screen exclusively for mass updating?

Thanks!
Blair

Okay ... so what might be bogging out my mass update commands, or how can I speed it up? 

Without going into all the code I've typed, I'm somewhat stumped on this one...

- I'm testing on 85,000 records with 2 subtable data fields
- I don't seem to have a lot going on in GLOBAL CODE
- I have a sort spec running for my subtables

Does this point to a bog-out point I could fix?

Thanks!
Blair

(T minus 6 days to going live...  )

No, I don't need to run the sort if I'm doing a mass update.  Is there some sort of condition like @mode() that I could put in my sort to prevent it just for mass updates?

Currently I'm building/testing on standalone.  Once the sales team is back in the office (their voice mail says Wednesday), I'll be snagging 25-30 licenses and (barring complications) start porting over my staff to Sesame next week.  My "server" is ready to go, and the staff have been getting weekly acclimatization sessions with the database in progress...