Hi Mark,

You've probably already figured this out, but each instance of a MTDLL creates its own independent environment regardless of the underlying object type so there should be little problem managing concurrencies. One 'best' practice would be to condition updates on a primary key and datestamp. Obviously, the only reason you'd want to use the VFP Session as the underlying object in a web environment would be to access the inherited props/events/methods.