1) The crash occurs even if I remove this attribute from the database and send it manually (separately from the application).
2) The crash doesn't occur on the 3.5 emulator when sending the database to itself. 3) What "modified database notification"? I use sysAppLaunchCmdExgReceiveData and then pretty standard stuff - ExgAccept, StrCaselessCompare, ExgReceive, ExgDisconnect, ExgDBRead, DmOpenDatabase, DmCloseDatabase, TimDateTimeToSeconds, FrmAlert, DmDeleteDatabase, DmQueryRecord, DmGetLastErr, MemHandleLock and MemHandleUnlock. Not all of them all the time, of course, but no others at any time during the database receiving. As far as I can see, none of the above requires anything newer than 3.0 (except the fancy stuff that needs 3.5 or 4.0 but I don't use any of that) - yet the crash happens under 3.5. Any other ideas? Regards, Vesselin -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
