Submitted by DavidF on 2016/11/19 14:17
hi,
 
I was going to post this in the Bugs forum but it clearly isn't really a bug as it is something that has gone wrong with a particular database. I'm putting it here as it relates to what is probably my main worry in my IQ usage - if there's a bug it will get fixed in the next version, but a corrupt database may be something I am stuck with. And even if Rebuild/Repair works I'd rather not have to keep on creating new versions. This is two or three times now I've had to recreate or copy a database in order to solve a problem or make the database usable. I'll confess, it worries me. Has anyone else had to go through this kind of routine to get a database working again?
 
Anyway, for what it's worth, here is how the problem manifested itself:
  • Text fields, with properties: auto-list of values, multi-select.
  • Checked values don't "stick". I check them, and when I open up the list again they are unchecked. New values that I add to the list disappear when I go back in.
  • This happens in all similar fields.
  • It only happens in this particular database.
  • Opening this database in an earlier version of IQ the problem is still there (ie it's not a bug that's just come in with the current version)
  • Did Rebuild Database then Repair and the auto-list fields seem to be working OK so far in the new version.
DavidF.

Comments

FWIW I never had to rebuild by IQBase, it is > 10 years old
 
It at all possible, scramble a malfunctioning one and send it over
 
 
 
Pierre_Admin
IQ Designer
 

DavidF

2016/11/20 13:35

Permalink

Will do. It's just one particular database, that is now at version 4... that is, I've had to recreate it 3 times. The first time was by copying and pasting, the last couple of times it was by rebuilding.
 
I'll be sending a copy your way.
 
DavidF.

Armando

2016/11/20 14:22

Permalink

[quote=DavidF]
Will do. It's just one particular database, that is now at version 4... that is, I've had to recreate it 3 times. The first time was by copying and pasting, the last couple of times it was by rebuilding.
 
I'll be sending a copy your way.
 
DavidF.
[/quote]
 
I've had the same DB for 8-9 years.
I've had very few DB problems along the years and only twice was it real "corruption" (one presumably because of crashes at the wrong moment, the other one was because of a script I wrote -- a very long time ago --  that was able to write on top of item ID numbers, which isn't possible anymore as Pierre protected a bunch of fields). A repair fixed the corruption.
 
Personnaly I wouldn't rebuild, just repair. A rebuild might only be useful if a repair fails. 
 
-
IQ geek
Windows 8.1
CPU: Intel i5 2.6ghz

DavidF

2016/11/20 14:56

Permalink

As I said in another post I've just recently discovered that Repair can actually fix things - but not in this case. Rebuild did the trick. Although, as per the instructions on the dialogue box, I Rebuilt, and then Repaired. Actually did this twice, as the problem (vanishing field values in popup lists) came back.
 
However as I've just explained to Pierre in sending him the offending database - the problem has now very inconveniently decided to stop happening. So who knows what's going on. Certainly, forever Rebuilding the db as a new copy would not be a workable solution to anything.
 
DavidF.

Armando

2016/11/20 15:18

Permalink

[quote=DavidF]
As I said in another post I've just recently discovered that Repair can actually fix things - but not in this case.
[/quote]
 
I haven't seen that in the previous posts & that's why I commented.
In the particular case I was thinking of, rebuilding or compacting before repairing made things worse.
 
-
IQ geek
Windows 8.1
CPU: Intel i5 2.6ghz