I've upgraded to the 3.6 (pre-release), and ran the repository scan, which is what I was after. It worked well by the way, we had some entries that looked pretty strange.

At any rate - now a form that we had been using won't save 'completely'. It starts to save, gets to 40%, and stops with a message saying 'save failed'. It actually looks like it saves the window record, but I think it is stopping on the compiling part. The executable hasn't changed (and still works as it did before this happened).

Any ideas what to look for? I would like to be able to salvage this screen.

Thanks,

Jeff

Jeff,

Did you rebuild your system indexes after the scan? Did you very carefully select what you were removing?

Cameron Purdy

Revelation Software

]] Did you rebuild your system indexes after the scan? Did you very carefully select what you were removing?«

I don't think I did rebuild, I didn't remember seeing anything about that - I'll try it in the a.m.

I was careful about what I removed - actually just a couple DBCOLUMNS entries that I already new looked bad - and the scan marked them as bad. It did seem however, that the scan program reports doing more than just the couple things I had selected. I would need to look at the log again. Is there a way to look at that after the fact?

My 'impression' with the window, is that something happened to a couple events we had defined. Although I can pull up the window in designer, the events don't appear to be there. Maybe reindexing the repository will help?

Jeff

Jeff,

My 'impression' with the window, is that something happened to a couple events we had defined. Although I can pull up the window in designer, the events don't appear to be there.

Try re-indexing the repository. Also, check the SYSREPOS record with the key "*OIWIN" … in field 6 (the "uses" relationships, SYSREP_SUB$ as defined by SYSREPOS_COL_EQUATES) you should find a list of the events for the form. Are those correct? (The form designer works off of this list.) It did seem however, that the scan program reports doing more than just the couple things I had selected. It corrects the uses/used-by relationships between entities. If an entity says that it uses another entity, but the second entity doesn't know it is used, then the tool updates the second entity to correctly "point back to" the first. OTOH, if an entity thinks that it is used by another entity but the second entity doesn't say that it uses the first, then the first entity has the "used by" information removed. When you run the scan with the "orphans" option, it will list any event entities that are not "used by" the corresponding form. There are one of two reasons given: 1. "Orphan" - the form or control that the event is tied to does not exist 2. "Orphan?" - the form or control that the event is tied to does exist but the form entity does not explicitly reference (the "uses" relationship) the event entity. In this case the scan tool isn't completely sure that the event is an orphan, although it will not be shown in the Form Designer. I would need to look at the log again. Is there a way to look at that after the fact? No. Cameron Purdy [email protected] </QUOTE> —- === At 16 MAR 1998 03:09PM Jeff Blinn wrote: === <QUOTE>Cam, Here are a couple facts we discovered that 'may' help: - Field 6 of the SYSREPOSOIWIN record does have the references to the events. - In designer, if I have this particular form on the screen, select the window, look at an event that is defined - I get a blank screen, as though there is no event. - In the SYSREPOSEVENTS file, if I look at the record - the code for the event actually 'is' there (which is good news as far as I'm concerned).

So . . . it looks like the link between the form and the actual event records is not correct. The events do show up in the repository, the code is in the event records, but in designer the events come up blank.

What do you think???

Thanks,

Jeff

View this thread on the forum...