"JB Parrett" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > A soft reset will fix this, but I know you would never depend on this to fix an error in code.
Oh, um, yeah, that's right... It turns out the problem was caused by not calling MemHandleUnlock/DmReleaseResource in one particular place. Too bad... I really wanted to use that SysReset function! David -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
