This is a massive grey area because you can preset, like Ted showed, or you can hide intentional.
I worry that you are not setting the rollback or commit when needed and in essence you could be defining a wall to shelter your data from others.
Are you setting only one connection and pushing all statements through it before you close it? Do you ever close a connection to a db in your code?
Found one of our SMEs kept on submitting statements against the db and only committing in the end. He put the table in lock mode until we rolled back a lot of his tests.
On Tue, Mar 1, 2016 at 10:24 AM, Chris Davis chrisd@actongate.co.uk wrote:
Hi All
If I start a SQL transaction and append records via a VFP View, issue a table update but don't COMMIT the transaction are these records available from another machine? If they are how could I know that they have been appended in a transaction that may well end up getting rolled back?
Thanks
Chris.
Chris Davis Acton Gate Systems Limited
We are moving! Please note our new address from 1st Feb Hilton Hall Business Centre Hilton Lane Essington West Midlands WV11 2BQ M: 07966 020473 *: chrisd@actongate.co.uk Webmailto:chrisd@actongate.co.uk%0bWeb: www.actongate.co.uk< http://www.actongate.co.uk/%3E
This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html
[excessive quoting removed by server]