Hi there, I have encountered what may be a bug. I have a form open in search/update mode that has a subform, when I type in a 'customer number' in the customer number field of the main form and an '..a..' in the description field of the subform(table view) and press F10, the client hangs with a red 'working' in the mode indicator and it crashes the server its on on our LAN thats running on a linux box. Once it actually crashed the box all together.
One interesting thing is that on the subform there is a 'spacer' field that is always blank and when I type an '=' in that field along with a customer number on the main form it doesn't cause any problems at all and retrieves all the records instantly.
Anyone else encounter something like this?
Thanks

Thanks for the prompt reply. The linux box is running Mandrake 10.1 with NCLib and the version of sesame is 1.1.3.

I will email the files to the support email asap. The forms that I have encountered this problem with are the invoice form and the customer form, let me know if you need further details for testing.

Thanks again.

Thats interesting about the invoice form not hanging. I just did a search on customer number 140103 and ..a.. in the Description field of the subform and it seemed to hang on my copy. Wierd.
The reason why we used relational linking is because we had to import invoice history into the existing app.
Thanks

Yes, I guess this app can be converted to natural now that we have all the data imported but we have other similiar appilcations having similar problems that have to stay relational unfortuneatly.

North Guy,

We found the problem in the Customers form. It wasn't actually crashing so much as it was running through all of the available memory. I've revised the relational subform search routine so that it will give back more memory as it runs, which should prevent the problem you are seeing in this form, and (in larger relational applications) improve the speed.

The fix will be in the next release.