I keep getting errors in the log file that only show up when using a programmed retrieve spec AND while a subform is present on the main form. This is the retrieve spec I'm using on the main form in a date element: ..{@date+30}

This is the info that shows up in the log file:
client_warning     S_ENG 460050     LocalLink:  The field name "Note" is not valid.
client_warning     S_ENG 460050     LocalLink:  The field name "Amount" is not valid.
client_warning     S_ENG 460050     LocalLink:  The field name "Category" is not valid.
client_warning     S_ENG 460050     LocalLink:  The field name "Name" is not valid.

The log file shows no errors when I search without a programmed retrieve spec. It also shows no errors if I remove the subform element from the main form, and then use the programmed retrieve spec. But when these two things are present at the same time, I get the errors in the log file.

Let me know if you need more info, or if have not made myself clear.

Edit:
BTW, running a search with the programmed retrieve AND subform present also causes the search/update view to freeze up in runtime. It does not usually freeze in preview mode though.

Bob,

No, I didn't forget about that. Thanks for checking with me though.

Actually, since posting that edit, I found that it is locking up in preview mode also. Furthermore, it seems that it is exibiting the same random freeze/not freeze behaviour in both runtime and preview modes.

Besides all that, I even removed every bit of programming from the main form and the subform just to be sure (using a test copy of the application, of course).

Quote:

Yes! You are correct. The errors went away after changing the field names for the subform.

But now the question is why didn't that cause a problem when using regular retrieve specs, as opposed to the programmed specs?

Quote:

541
684
Natural

Quote:

Sesame did not freeze. The Search/Update view (or tab) froze. I could still use the Application tab or my custom main menu tab. Only the view of the Search/Update tab for the form I was performing the search in, would be frozen. I could still click on the "Record Navigation Toolbar" to navigate through the result set, but the form view did not show anything but the search screen with the retrieve specs. The "Search/Update Menu" tree showed, but would not accept any mouse clicks. If I minimized Sesame and then restored it's window, the area where I should see the form just showed the portion of my desktop that was in that area while Sesame was minimized. If I clicked on the Application tab so that the splash screen showed, then clicked back on the Search/Update tab, I would still see the splash screen. Likewise, if I clicked on the tab for my custom main menu, then back on the Search/Update tab, I would still be looking at a view of my custom main menu.

Maybe I should have said that the tab did not update it's view vs. saying that it froze.

Carl,

I can only speculate as to what it might be at this time. I'd have to have a look at it to see.

If you could send me your DB and DAT files I will have a look at this and see if I can get the tab to freeze up.

-Ray

Ray,

I'm pretty sure I found what was causing the Search/Update tab to not update it's view.

This is strange to me, but maybe it will make some sense to you or someone else there at Lantica. I had to disable hyper-threading in my system BIOS to get the problem to go away.

Do you think that hyper-threading might have had something to do with Sesame crashing on me last night as well?

FYI: Hyper-Threading Considered Harmful
Quote:

As with all Internet information, consider the source.
From: http://www.daemonology.net/hyperthreading-considered-harmful/

Quote:


Sesame is a multi-threaded application, and will take advantage of multiple processors, hyperthreading, or multi-core. If you are running standalone, the client, server, and the communications are each handled by separate threads. If you are running client/server, all of the above and each individual command sent from the client to the server is handled by separate concurrent threads.

I have to take back what I said about disabling Hyper-Threading. Since disabling it, I have been experiencing more problems with Q&A in one evening than I have in the last few years! At least three crashes or lock ups in as many hours! (I just hope it's not the new video driver causing these problems.)

I read in Microsoft's Knowledge Base that if Win XP was installed with HT enabled, there could be problems if you later disable it. But that was supposed to be resolved in Service Pack 2, which I do have installed. Maybe there is still something that wasn't taken care of in SP2.

Ray,

Quote:

Sure.

1) Starting at the custom main menu, select the command button labeled "Search" .

2) Open the spec manager and select the "View Payables" retrieve spec.
(Sometimes I would paste "..{@date+30}" into the date element rather than load the saved retrieve spec.)

3) Close the spec manager and press F10.

I also was repeatedly pressing F7 and F10 to rerun the search, because sometimes it froze on the 1st run, and sometimes it took a few tries.

I'm not sure that you will be able to reproduce the problem. I just ran that search 50 times in a row without any abnormal results. But, good luck.

If there's anything else I can help with, let me know.