I am customizing RMS to have Patient Record System (PRS) for an optical shop. It will keep track of all the prescriptions made in the stores (frames, lens, etc). I am thinking of creating a new table that will hold this data. But what I want is that the prescriptions made in a particular store must also be available/visible to the other stores. This maybe done by synchronizing this data to the HQ and back to the stores. How can I do this? Please help..
Custom Table synchronizing..
Feb 08, 2006
4 Replies
There is a TableSync table you can utilize to transfer and aggregate custom tables from stores to HQ, but one store's data will not be viewable at other stores. To achieve this you would need to use some more complicated worksheet 51's or DTS packages.
- Evan Culver New West Technologies
Ij> I am customizing RMS to have Patient Record System (PRS) for an optical shop.
You need to create a record in the TableSync table: TableName = Name of table to upload or download ToHQ = 1 if to upload, 0 if not ToStore = 1 if to download, 0 if not Options = See translate table below. The tables to be uploaded and downloaded must follow these conventions:
- They must exist at both HQ and the Store as the same name
- If uploading to HQ, the table must contain both an ID field and a StoreID field. The ID field must have the IDENTITY attribute at the store and not at HQ.
- If downloading from HQ to the store, the table must have an ID field with an IDENTITY attribute at both HQ and the Store and a HQID field at both locations.
- The tables must contain a DBTimeStamp field that is the TimeStamp for the record.
- The TableSync data will be processed for each Data Upload worksheet, immedeiately after the transaction data has been uploaded. Translate Table Options: The data in the tables uploaded to HQ can be translated to maintain the proper links. The following table describes the translate options: Value Meaning
0x0001 The AccountTypeID field will be translated for HQ 0x0002 The CurrencyID field will be translated for HQ 0x0004 The CustomerID field will be translated for HQ 0x0008 The ItemID field will be translated for HQ 0x0010 The ItemTaxID field will be translated for HQ 0x0020 The ShippingCarrierID field will be translated for HQ 0x0040 The ShippingServiceID field will be translated for HQ 0x0080 The ShipToID field will be translated for HQ 0x0100 The SupplierID field will be translated for HQ 0x0200 The TaxID field will be translated for HQ 0x0400 The TenderID field will be translated for HQ 0x0800 The DailySalesTypeID field will be translated for HQ 0x1000 The ReasonCodeID field will be translated for HQ 0x2000 The DiscountReasonCodeID field will be translated for HQ 0x4000 The ReturnReasonCodeID field will be translated for HQ 0x8000 The TaxChangeReasonCodeID field will be translated for HQ These values can be OR'd together to translate more than one field in the uploaded table."Ij> do you know guidelines/procedures in using tableSync?
Join the Discussion
Have something to add? Share your thoughts — no account required.
Didn't find your answer?
Ask the community — no account required