Good evening, I am newly signed up but have been lurking on here for awhile. I am on a bit of a time crunch and don’t have the time to experiment so I thought one of you may have already ran into this situation and found a solution. I saw this post and figured this was a good time to jump in.
Let me give you a little background on the situation. We use Clarion 6 and we handcode, we do not use ABC templates. We are wanting to migrate from .dat/tps files to MSSQL. The current .dat/tps tables are in use 24/7 (manufacturing plants). We want to write to both the .dat/tps files and the MSSQL tables at the same time as the first step in this transition.
We attempted this last year and the workstations on the production floor threw errors (This process works correctly in both our Dev and Tst environments.) There was ‘panic in the streets’ and they immediately ‘rolled back’ to a previous Clarion build and did not provide us with any feedback. I have a slight opening in my work load and have been assigned to revisit this week.
In order to generate feedback but not cause the panic, I am logging any error that is received, setting a global variable and if the global variable is set to false than the code that writes to the tables will not attempt to write to MSSQL. All of this is working.
The problem is that the user receives the Microsoft SQL error and I have not been able to figure out a way to suppress this.
My code is an extension that sets the base variables and then a .inc that pulls together the login info, server name, etc. I then do a simple OPEN() call. Immediately afterwards I have Error() handling which works fine but of course it doesn’t handle the Microsoft error. Is there any way to suppress these?
Thank you for your time.