T
temays
Guest
Sounds like you have checked everything on the Pro2 side. If the TableXref.genQRec flag is true, and the triggers are properly inserted, you should be seeing replqueue records. My suggestion is to verify the trigger is actually running. Maybe open and close a file within the trigger code. Did you see the file get created? Be careful of doing this in a production environment. If the table in question is heavily transacted, the opening/closing of an OS level file could really slow down the application. Another thing to check would be if the the application uses SCHEMA CACHE files (-cache client side startup parameter.) If -cache in play then I would suggest this is your issue. Simply inserting triggers and pointing to an old cache file would allow the user session to not even recognize a trigger has been inserted. If this is the case, you'll need to generate a new cache file (search the docs for SAVE-CACHE) and then distribute the new file to the application. Terry Mays
Continue reading...
Continue reading...