Hi all, (17.0.11.7458)
We have a Mobilink project again after 15 years or even more than that. Luckily an easy one, only two remote databases. Since it's been so long, I can no longer remember some of the options, so:
I know that for a time, output ...
Hi, SQL Anywhere 11.0.1.2878
This is going to sound a bit abstract - the client has noticed that, incredibly rarely, one simple process of marking 10-12 table rows with a flag does not get committed to the DB. They are accessing it via Powerbuilder a...
Hi, upgrading SQL Anywhere with latest EBF from 17.0.11.7059 to 17.0.11.7254.
Went just fine on two laptops running Windows 10 Pro fully updated.
But on our Test server (Windows 2019 Server standard) the EBF installation fails with error message
**C...
Hi,
We are having problem with SQL Anywhere 17 (latest build) and ADO.Net entity framework in Visual Studio 2019 - we are trying to set up the EF provider with Visual Studio 2019. I believe we managed to do it for Visual Studio 2012 (with SQL Anywhe...
Hi, SQL Anywhere 17.0.11.7058
We have a database with CHAR encoding set Western Latin 1252, and NCHAR encoding set UTF-8 which is giving us a problem when we are exporting some NVARCHAR non-English characters. We are doing this by using UNLOAD SEL...
I just tried this, and it's a bit odd that when I run mlsrv17.exe and dbmlsync.exe as executables from batch file, there is indeed the log window shown on the desktop which you can minimize to system tray or leave running on the screen. But I can't g...
Huh. Guess my memory is poorer than I thought, but good to know that you can actually get them back as desktop-bound log windows.
I'll have a look at the docs about report_error. I remember that after a while we got our mobilink scripts foolproof, ...
Thanks Reg,
John replied just before you with a similar suggestion to include the -d (-hd) switch, which I did.
In any case, you are correct that there are TWO Rollbacks in my initial dbtran translated log. It goes like this:
--ROLLBACK-1030-048600...
Thanks John,
I did a trace as you suggested with the -hd option.
There is no mention of Release around 0486009518 or indeed, anywhere in the log translation. In the meantime, Reg has replied further below with a good guess - if there were actually t...
