I didn't realize I could get more info from DmGetLastErr. In any case, I
found the problem. The app that was doing the modification didn't do
anything wrong, but an app I ran previously which converted the database to
a new format did - it didn't release records that it changed.
To answer your question, I don't do a DmGetRecord unless I intend to change
the record. In this case, the initialization function of the form just
needs to read the record to populate the form with the correct initial
values, so I do a DmQueryRecord instead.
Thanks!
Mark Peters
> From: "Peter Epstein" <[EMAIL PROTECTED]>
> Newsgroups: palm-dev-forum
> Date: Fri, 24 Mar 2000 14:49:06 -0800
> To: palm-dev-forum
> Subject: Re: DmGetRecord timing/initial condition problem?
>
>
> The error message you're seeing ("Err getting rec") could be caused by
> several things. The actual error can be determined by calling DmGetLastErr.
> It'll either be dmErrIndexOutOfRange (if the index is bad) or
> dmErrRecordBusy (if the record was already busy from a previous call to
> DmGetRecord without a matching call to DmReleaseRecord. Is there some reason
> why you're not just calling DmGetRecord when your edit form starts up?
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
