![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 6 of 6 total |
![]() |
Fri, Oct 31 2014 10:20 AM | Permanent Link |
Richard ENT Technologies | Hi,
I have an old database, using Delphi 5 and DBISAM version 3.27. Today, one of my users started getting this message on just a handful of tables in the database. Is there a way to correct this problem? I have DBISAM 4 and XE4, so I thought about trying to upgrade the faulty table to version 4, dumping the data, recreating the version 3 table and importing the data back in. Thanks |
Tue, Dec 9 2014 12:31 PM | Permanent Link |
Fernando Dias ![]() | Richard,
Have you tried to repair the tables with DbSys? If not, give it a try - the tables might be corrupt. If DbBSys cant correct it, then your idea seem to be a good idea, but if the tables are seriously damaged you might not be able to convert them to V4. -- Fernando Dias [Team Elevate] |
Tue, Dec 9 2014 8:04 PM | Permanent Link |
Raul ![]() | On 10/31/2014 10:20 AM, Richard wrote:
> I have an old database, using Delphi 5 and DBISAM version 3.27. Today, one of my users started getting this message on just a handful of tables in the database. > > Is there a way to correct this problem? I have DBISAM 4 and XE4, so I thought about trying to upgrade the faulty table to version 4, dumping the data, recreating the version 3 table and importing the data back in. Any chance somebody tried to open it with the DBISAM 4 engine (either using newer dbsys or ODBC driver or such) ? Easy way to check is to get a copy of the problem table and see if it opens with your copy of dbsys v4 - if it does without any issues then table has been upgraded already (and it cannot be downgraded except dumping the data and loading into empty v3 table) I have not had to do an upgrade for a long time but i recall it being silent so just by opening it once you might upgrade it. Raul |
Wed, Dec 10 2014 3:17 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Raul
I'd pretty much go along with you but add - did one of the users reinstall an older version of the table? Roy Lambert |
Wed, Dec 10 2014 8:25 AM | Permanent Link |
Raul ![]() | On 12/10/2014 3:17 AM, Roy Lambert wrote:
> I'd pretty much go along with you but add - did one of the users reinstall an older version of the table? Good point Roy, I guess mix of tables and/or even restoring partial files (like the blb or idx only) ore even good old file corruption could do this also. Checking the file dates would be 1st step to make sure there is no significant date difference for table files. Sending copy of the tables to elevatesoft support is the only 100% certain way to find out what exactly is wrong with the tables. Raul |
Wed, Dec 10 2014 8:58 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Richard
I just had a look at my antique (4.25b5) DBSys and Ultilities | Table Version should at least tell you what version DBSys thinks it is, Roy Lambert |
This web page was last updated on Wednesday, August 14, 2024 at 03:12 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |