Works just fine. I was able to create a generic CRecord class that handles most of
the Dm* calls that I use right now. It actually works very well, and the nice thing
is that you don't have to worry about any of that *!@# memory management stuff because
you do it once and then get to forget about it!
[EMAIL PROTECTED] wrote:
> I'm looking for ideas here. Maybe someone out there has figured this outbefore and
>is willing to share :)
We're C++ programmers and many of the applications we build (non-PalmOS) use
back-end databases for status and configuration data. We've always build
classes representing a record in a database table with accessor methods for
the fields. We also have methods to load, update, insert, and delete the
database records. Basically...
class DBRec
{
public:
...
// accessors
int id (void) const { return m_id; }
void id (int i) { m_id = i; }
...
// database manipulators
bool load (int i); // populates the object with data from
// the corresponding database record
// (i.e. "select ... where id=i")
...
};
I'm thinking of coming up with such an animal for our PalmOS apps to wrapper
the Dm* calls that we're using. Any suggestions? Ideas? Reasons it won't
work?
TIA,
-Paul
____________________________________________________________________________
Paul Dugas Computer Engineer | http://pauld.dugas.com/
mailto:[EMAIL PROTECTED] Dugas Enterprises, L.L.C. | TEL +1-404-624-7840
1711 Indian Ridge Drive, Woodstock, GA, 30189-6856 | FAX +1-404-635-8001
