Link to home
Start Free TrialLog in
Avatar of VirtueTech
VirtueTech

asked on

On a "TTAble.Open" command I get "Capability not Supported"

Hello everyone,

I keep getting the error when I execute my script "Capability not supported".

When I traced into the error it happened at:   TTable.Open;

The TTable object is trying to open a DB2 database table using the EasyCom ACE400 dirvers...reading the table...then writing to a paradox table.

I am using:
-  Delphi 7
-  BDE 5.01
-  DB2 Database
-  Paradox

Please help....
Avatar of VirtueTech
VirtueTech

ASKER

Do I need to change .Open to another method?
Avatar of kretzschmar
i could only guess that there may a problem with a fieldtype

could you provide your db2-table structure?
Did you try TTable.Active:=true; ?
I tried Active = true ...didn't work...I get the same error
It happens as soon as I go to Open the table so I don't think it would be a field type within the DB2 database.
It used to work fine.

Yesterday someone removed the BDE from our system. Then this all started to happened.

When I upgrade the BDE from 5.01 to 5.2.02 it still says in the "about" page that the version is 5.01 even though the version in the properties dialog window for the BDEadmin.exe file is 5.2.02

Any other ideas?
I called Borland and they don't have any clues as to why this is happening.

Please help ...anyone :)
ASKER CERTIFIED SOLUTION
Avatar of VirtueTech
VirtueTech

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
PLEASE  CLOSE  THIS  QUESTION
I ran into the same error message, but found a completely different solution. I also got the "Capability not supported" error at a TTable.Open command. I am using:

- Delphi 5
- BDE 5.01
- dBase IV tables

In my case, the error was caused by a corrupted temporary dbf file. Although Delphi should delete all of the temporary dbf files when an application closes, it is really sloppy in this area. Once I manually deleted the temporary files, the error message went away and the application worked as normal again.