You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was honored to inherit a legacy application from a college that left. The application is written in Borland C++, using a firebird database.
The problems are that when you run queries and commit it to the database; I get the following error message.
"Error : Dynamic SQL Error SQL error code = -204 Table unknown NUMBER at line 1, column 152"
Now NUMBER is a column in a table and not a table itself.
Now the killer is, it only happens on certain PC. All are XP service pack 2, but I can't seem to find a difference that indicates what the problem is.
The fact that it only happens on certain PC makes me believe it is a environment / setup error, so before I start hacking into the code that is undocumented I thought to ask if anyone had something similar to this before, and if so what is the problem en how can we fix this.
All help will be appreciated
Kind regards
Schalk
The text was updated successfully, but these errors were encountered:
Submitted by: Schalk Lotz (schalklotz)
Duplicates CORE990
I was honored to inherit a legacy application from a college that left. The application is written in Borland C++, using a firebird database.
The problems are that when you run queries and commit it to the database; I get the following error message.
"Error : Dynamic SQL Error SQL error code = -204 Table unknown NUMBER at line 1, column 152"
Now NUMBER is a column in a table and not a table itself.
Now the killer is, it only happens on certain PC. All are XP service pack 2, but I can't seem to find a difference that indicates what the problem is.
The fact that it only happens on certain PC makes me believe it is a environment / setup error, so before I start hacking into the code that is undocumented I thought to ask if anyone had something similar to this before, and if so what is the problem en how can we fix this.
All help will be appreciated
Kind regards
Schalk
The text was updated successfully, but these errors were encountered: