RE: OpenOffice, Go-OO, ODBC, Offline Data Entry

2010-08-19 Thread Lord_Devi
> >> Is this foolproof? Absolutely not, if there are conflicts between the > >> changes > >> by different users. You'll be stuck with "He who write last, writes best"; > >but > >> I think that's as good as it's going to get for you. > > > >AIUI, you could prevent that by having a second timestamp,

RE: OpenOffice, Go-OO, ODBC, Offline Data Entry

2010-08-19 Thread Jerry Schwartz
>-Original Message- >From: Joerg Bruehe [mailto:joerg.bru...@oracle.com] >Sent: Thursday, August 19, 2010 7:25 AM >To: mysql@lists.mysql.com >Cc: Jerry Schwartz; 'Lord_Devi' >Subject: Re: OpenOffice, Go-OO, ODBC, Offline Data Entry > >Hi! > >

Re: OpenOffice, Go-OO, ODBC, Offline Data Entry

2010-08-19 Thread Joerg Bruehe
Hi! Jerry Schwartz wrote: > I deal with a somewhat similar situation. Even though we have fast VPN > connections among our various offices, each has been afflicted with a > different database structure (and software) which they cannot change. > > What I suggest you do is use the kind of "pseud

RE: OpenOffice, Go-OO, ODBC, Offline Data Entry

2010-08-18 Thread Jerry Schwartz
I deal with a somewhat similar situation. Even though we have fast VPN connections among our various offices, each has been afflicted with a different database structure (and software) which they cannot change. What I suggest you do is use the kind of "pseudo-synchronization" that we do. Use a