Skip to main content

[Migrated content. Thread originally posted on 12 July 2005]

hi everyone,

this time i am trying to bring visionfiles into an MSSql-Server.

The programm is running so far, but a few files causes errors, and i dont understand whats wrong.

One code is 9D,1909
It happens when i use the "open output" command for a SQL-Hosted File.
If i (after this Error) look into the SQL-Server, the table has been created and looks correct.

The other code is 9D, 10038
It happens on the first "write" command (this time the open command was successful)
If i this time look into the SQL-Server, the table is still empty.


anyone any suggestions?
(All nonworking files are small, with not to much columns or keys)

[Migrated content. Thread originally posted on 12 July 2005]

hi everyone,

this time i am trying to bring visionfiles into an MSSql-Server.

The programm is running so far, but a few files causes errors, and i dont understand whats wrong.

One code is 9D,1909
It happens when i use the "open output" command for a SQL-Hosted File.
If i (after this Error) look into the SQL-Server, the table has been created and looks correct.

The other code is 9D, 10038
It happens on the first "write" command (this time the open command was successful)
If i this time look into the SQL-Server, the table is still empty.


anyone any suggestions?
(All nonworking files are small, with not to much columns or keys)
I tried hundreds of things and found this (for error-code 9D, 10038) :

the write-command creates one record before the runtime dies.

i have (as example) one field defined as:
pic x(256).

A look into the sql-table shows this as content of the field:
"junkdata".

Why this? If a field exceeds 255 it should be translated to a "text"-Field. The SQL-Server shows, that this had correctly happend.
So why is the column filled with "junkdata"?

And how can i get around this problem?

[Migrated content. Thread originally posted on 12 July 2005]

hi everyone,

this time i am trying to bring visionfiles into an MSSql-Server.

The programm is running so far, but a few files causes errors, and i dont understand whats wrong.

One code is 9D,1909
It happens when i use the "open output" command for a SQL-Hosted File.
If i (after this Error) look into the SQL-Server, the table has been created and looks correct.

The other code is 9D, 10038
It happens on the first "write" command (this time the open command was successful)
If i this time look into the SQL-Server, the table is still empty.


anyone any suggestions?
(All nonworking files are small, with not to much columns or keys)
Regarding your error 9D,10038 - the error message that you are getting actually means that you there is a problem updating a row/column because of its size. If you set the Acu4GL for MS SQL Server configuration variable A_MSSQL_EXTRA_PROC to "1" this will solve your problem.

[Migrated content. Thread originally posted on 12 July 2005]

hi everyone,

this time i am trying to bring visionfiles into an MSSql-Server.

The programm is running so far, but a few files causes errors, and i dont understand whats wrong.

One code is 9D,1909
It happens when i use the "open output" command for a SQL-Hosted File.
If i (after this Error) look into the SQL-Server, the table has been created and looks correct.

The other code is 9D, 10038
It happens on the first "write" command (this time the open command was successful)
If i this time look into the SQL-Server, the table is still empty.


anyone any suggestions?
(All nonworking files are small, with not to much columns or keys)
@Dilbert
Sorry .. had no effect.

I've send the problem to the support. I hope they can find it.

[Migrated content. Thread originally posted on 12 July 2005]

hi everyone,

this time i am trying to bring visionfiles into an MSSql-Server.

The programm is running so far, but a few files causes errors, and i dont understand whats wrong.

One code is 9D,1909
It happens when i use the "open output" command for a SQL-Hosted File.
If i (after this Error) look into the SQL-Server, the table has been created and looks correct.

The other code is 9D, 10038
It happens on the first "write" command (this time the open command was successful)
If i this time look into the SQL-Server, the table is still empty.


anyone any suggestions?
(All nonworking files are small, with not to much columns or keys)
@Dilbert
Ups .. sorry .. your hint was right.

I have to set it in the config-file and not in the source, and then it works perfectly. :D
Terms & ConditionsAccessibility statement