Unable to access Records within a Table (OpenInsight 32-bit)
At 06 SEP 2012 02:52:09PM Ray Chan wrote:
We have a single-user client site (OI 808 and Windows 7) that cannot access records within a Table.
There are no indexes on this table (I removed them). I can run a report, e.g., Slist, and keys will show. However, if you try to bring up a record, you'll get a message that basically says that the Record in the table was not found.
I can't figure this out. Any idea on what happened? I've not seen this before.
Thanks,
Ray Chan
At 06 SEP 2012 05:02PM Jared Bratu wrote:
Here are some questions to narrow down the problem.
Are you trying to open the record with the system editor or your form? Is there any difference with the system editor?
Have you checked for group format errors?
What network driver are you using?
At 06 SEP 2012 05:36PM Ray Chan wrote:
Hi Jared,
This is a single-user so there is no network driver in play.
If I use a non databound form to bring up the record, we get an error. The read is unable to read the record.
If I use the system editor, it tells me taht the record is not found.
However, if I List the table, I can see the keys, then when I go to the system editor NOTHING???
Isn't this strange?
I didn't check for GFE since I didn't see any thing unsual above 2. It's been a long, long time since I've encountered any GFE with OI. I just got back into the client system and check. Sure enough there is a GFE.
But when I tried to repair it I'm getting an FS255. The Group is 2242 and the Code is 9.
Thanks,
Ray
Does this picture help?
Ray Chan
At 07 SEP 2012 04:28AM bill caisley wrote:
Hi Ray,
FS255 = An error has occured while attempting to create the DUMP_FIX_TEMP table. This table has not been attached in the app or does not exist.
At 07 SEP 2012 09:30AM Jared Bratu wrote:
The network driver always comes into play. When there is no server the network driver provides the local file I/O. If you were using the All Networks Driver 1.5 I would be concerned. Although the 2.1 isn't supported it's still widely used. Ideally you should be using the Universal Driver.
To fix the FS255 error you'll need to check the DUMP_FIX_TEMP and DUMP_FIX_GARBAGE tables. These tables are used during the repair process and sometimes aren't properly attached. Try to attach them, if they can't be attached go ahead and create empty tables with those names and attach them before starting the repair process.
At 07 SEP 2012 10:22AM Ray Chan wrote:
Thanks guys,
I don't have access to the client system right now. When the client calls me back, I'lll remote in and add these tables and see what happens.
I hope fixing the GFE will fix this problem. As I mentioned, I haven't seen a GFE in a years (??) – seriously a long long time.
Ray Chan
At 07 SEP 2012 08:21PM Ray Chan wrote:
Just to follow-up. I got connected to the client site and created the two tables: DUMP_FIX_TEMP and DUMP_FIX_GARBAGE and was able to repair the GFE. After this, the client was able to access items in the file.
Thanks for your help!
Ray Chan