Hi Carl -
The PrimeFields method that gets called in the update form is part of the WindowManager object. I don’t think the dictionary has anything to do with what gets done with that. I always thought of it as an extra place to set stuff up after the record had already been created/primed by the browse object.
The FileManager.PrimeRecord() does make use of the dictionary stuff, I think. It gets called from the browse (if there is a browse). I suppose you could try Access:YourTable.PrimeRecord() , but for single record scenarios, I’ve always put the code in that setup code. You have a good point though.
In my experience, usually a single record table is written once and read often. But I suppose it could be important to support the optimistic concurrency issues too for some situations.