unsubscribe please, once and for all On Wed, Aug 18, 2010 at 6:03 PM, Drew <[email protected]>wrote:
> On Wed, 2010-08-18 at 10:08 +0300, Lars Nooden wrote: > > On 08/18/2010 09:29 AM, Lord_Devi wrote: > > > Here is the catch. The SQL database itself exists at a 'home office', > > > and these workers are wanting to be able to enter this data remotely; > > > in an 'offline mode' as it were. > > > > Some kind of local cache is needed. As you point out the difficulty is > > with updating the central database. > > > > The update could be > > > > + triggered manually, putting the onus on the user to remember to do so > > once connected. > > An example of this in Base would be: > There would be 2 odb files. > - One connects to the 'office server' database, call it office.obd. > - One uses the embedded HSQLdb engine for the 'mobile desktop' and call > this field.odb. > Each has a table named 'Transactions', with a common structure. > Updating manually then consists of: > -opening both files on the desktop > -drag the Transactions table from the field.odb window to the office.odb > window. > -drop the table object onto the Tables section. > -in the export data dialog that opens select, append data > -click finish > (in practice you might use a view in the field.odb for the transfer, to > make key handling easier) > -Open the Transaction table in the field.odb database, select all > records and delete them. > OK - so that is a zero coding solution (well, not counting creating a > view perhaps) > > > > > + attempted regularly via cron > > > > + triggered via a script launched by the interfaces configuration once > > network connectivity is regained > > next email.... > > > > > > > I don't know if maybe having a local SQL database running on each > > > worker laptop which could somehow 'sync' the data would be a viable > > > option or not... That is something I have never tried before. > > > > > http://wiki.services.openoffice.org/wiki/Documentation/How_Tos/Using_SQLite_With_OpenOffice.org > > > > > ... they may have to enter the data twice: Once on-site, and a 2nd > > > time when they get back to the office. Essentially copying the > > > offline data, into the 'live' forms essentially. > > > > Not a good choice. That wastes more than work. A central rule of time > > management is to touch each piece of paper only once -- ever. > > > > /Lars > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
