FiveTech Software tech support forums

... approach at achieving replication: 1. have a way to declare a "publication". A publication describes what tables & columns are to be replicated. A single database could potentially contain various publications with different sets of tables to be replicated. 2. have a way to declare ...

... The corresponding table on the replication server should be identical with the main table. Then any changes made to the main table will be replicated to the same table on the replication server. This is the functionality we attempted to create. Please test and share your observations.

... printer. The customer can print invoices or estimates and it works perfectly The customer can no longer print counter sales. The problem cannot be replicated at any other client or in house. When he put the old printer back on line, it now cannot print counter sales. Again the same function is ...

... is written to both servers or none at all. In the case of single server, nothing can be written if that server is off. Same way in the case of replicated rowset, nothing can be written if both the servers are not working, i.e., if one of the servers is off. Replication can be turned off by ...

Dear Rao Sir ,

Just wanted know if in case Replication sever is off/failed and after some time when it becomes live then how it is replicated the in between changes ? OR we need to manually runs any jobs to update ? OR may be some other way work around ?


Thanks
Shridhar

... This feature helps backing up each transaction as and when it occurs. Requisites: 1) The DBF should contain an AutoIncrement field. 2) Exact replicated table with the same name should exist on the replication server. Initially, this can be easily setup by calling oCn:ImportFromDBF( cDBF ...

... This feature helps backing up each transaction as and when it occurs. Requisites: 1) The DBF should contain an AutoIncrement field. 2) Exact replicated table with the same name should exist on the replication server. Initially, this can be easily setup by calling oCn:ImportFromDBF( cDBF ...

... to the same table on the remote server also. Conditions: Do not change the table with your own SQL statements. Do not directly modify the replicated tables on the remote server. \fwh\samples\mariarpl.prg #include "fivewin.ch"function Main()   local oMain    := FW_DemoDB()  ...

... to the same table on the remote server also. Conditions: Do not change the table with your own SQL statements. Do not directly modify the replicated tables on the remote server. \fwh\samples\mariarpl.prg #include "fivewin.ch"function Main()   local oMain    := FW_DemoDB()  ...

... on the Browse, the old data is still present ( if I call a xBrowse(oDbDat) after assign oDbDat:=oDbNew to check it, the new data is there, but no replicated in the Browse) Any Ideas FWH 17.04

...       := oBrw1:nColSel      :nColOffset    := oBrw1:nColOffset      //      :Refresh()   ENDreturn nil  Navigation in either browse is replicated in the other browse.

... C interface (HDO from Exposito for ex). adordd can work with any other class as long as the few methods and data adordd use from MS ADO are replicated in that class. This class could build the sets in a local dbf files, arrays etc.

... If I Reactivate the Window Style, The Group's brush is lost only on the initial painting of the window, and then is OK... This behavior can be replicated by just using this style in samples\Ribbon.prg

Is your requirement one way synchronization of master table on server to replicated table on local pc? If so, I suggest a different solution. Maintain UpdateTimeStamp column in the Table. When you want to synchronize, <psuedo logic> Step1: Select Max( ...

Is your requirement one way synchronization of master table on server to replicated table on local pc? If so, I suggest a different solution. Maintain UpdateTimeStamp column in the Table. When you want to synchronize, <psuedo logic> Step1: Select Max( ...