From: Oliver G. <oli...@we...> - 2001-11-09 22:26:55
|
Hans Ajiet Holtkamp wrote: > I am not sure what a conduit is, but if > you are referring to an Access/Excel As far as I understand it, a conduit is a piece of software that manages the synchronization of data when a Palm is synced with the desktop computer (loke AvantGo Connect for example). The Palm desktop software does this for the built-in applications of the Palm (Calendar, Address Book, etc.), but for proprietary software this synchronization ability has to be provided as such a conduit. Of course the DB databases are already synched to the Backup directory on the PC if they have been changed, but by default the syncing software can only do that for a whole database because it has no knowlegde about the data inside it. The tricky part for such a conduit would be to manage the synchronization on a per-record basis, so that you can modify records on the Palm as well as on the desktop database application. The data of these two modified databases would then have to be merged together to represent the changes that were made on either side. This could only be done if the conduit had a means to decide which records have been changed on Palm or on Desktop side, and in case the same record has been changed on both sides, which is the valid version (this can be very tricky, because one can think of different scenarios where different strategies could be applied). Personally, I'd rather see something more generic than an Access conduit, simply because I don't use Access. But I'm not sure how such a solution could look like. Maybe something that can use CSV-Files on the PC side or a Java based conduit which would allow to use JDBC to connect to any relational database rather than a proprietory solution which only works on one specific database system. (Or maybe ODBC could be used for database access on the desktop computer). Cheers, Oliver -- Oliver Goetz, mailto:oli...@we... "I'd rather laugh with the sinners than cry with the saints Sinners are much more fun... And only the good die young" -- Billy Joel |
From: Larry K. T. <LK...@we...> - 2001-11-12 17:49:24
|
This explanation of a conduit is exactly what I was asking about. And I'm = not suggesting that someone stop development on pilot-DB to work on this. = I was really just fishing for information as to weather anyone was working = or thinking about working on this. Currently I use Think-DB with DB-Sync, but I like some of the pilot-DB bett= er than Think's As to a CVS type conduit, I can get to this type of data almost as easily a= s a standard Access DataBase. Larry >>> Oliver Goetz <oli...@we...> 11/09/01 05:27PM >>> Hans Ajiet Holtkamp wrote: > I am not sure what a conduit is, but if > you are referring to an Access/Excel As far as I understand it, a conduit is a piece of software that manages the synchronization of data when a Palm is synced with the desktop computer (loke AvantGo Connect for example). The Palm desktop software does this for the built-in applications of the Palm (Calendar, Address Book, etc.), but for proprietary software this synchronization ability has to be provided as such a conduit. Of course the DB databases are already synched to the Backup directory on the PC if they have been changed, but by default the syncing software can only do that for a whole database because it has no knowlegde about the data inside it. The tricky part for such a conduit would be to manage the synchronization on a per-record basis, so that you can modify records on the Palm as well as on the desktop database application. The data of these two modified databases would then have to be merged together to represent the changes that were made on either side. This could only be done if the conduit had a means to decide which records have been changed on Palm or on Desktop side, and in case the same record has been changed on both sides, which is the valid version (this can be very tricky, because one can think of different scenarios where different strategies could be applied). Personally, I'd rather see something more generic than an Access conduit, simply because I don't use Access. But I'm not sure how such a solution could look like. Maybe something that can use CSV-Files on the PC side or a Java based conduit which would allow to use JDBC to connect to any relational database rather than a proprietory solution which only works on one specific database system. (Or maybe ODBC could be used for database access on the desktop computer). Cheers, Oliver --=20 Oliver Goetz, mailto:oli...@we...=20 "I'd rather laugh with the sinners than cry with the saints Sinners are much more fun... And only the good die young" -- Billy Joel _______________________________________________ Pilot-db-list mailing list Pil...@li...=20 https://lists.sourceforge.net/lists/listinfo/pilot-db-list |