Wizarded Browse/Form - Clarion crashing

[Keith]

Hi

I have in my dictionary two tables 'Customers' and Bookings' that are related 1:many on Customer and Booking numbers.

I defined a new table and relationship as follows:

'BookedPets' with 3-component key and related it to 'Bookings' (1 Booking:Many Pets) - See Pet5.png

In my app I then chose 'Add Procedure'/Browse Wizard to create the procedure 'bBookedPets' with option to generate the Form.  After 'Finish' this gave the error in Pet3.png.  After hitting 'Ok' Clarion crashed - Pet5.png

I redid this many times in a variety of scenarios and the bit that caused the errors was the defining of the relationship between 'Bookings' and 'BookedPets'.  If that is removed then everything is sweet.

I have also used the 'Default' tab NetWebForm with same result.

Thanks for your assistance.  Note: I couldn't actually upload the images because  'the upload folder is full'.  I'll try again later

Keith

[Bruce]

Hi Keith,

I'll likely need to see your app and dict to determine what it didn't like.

Cheers
Bruce

[Keith]

Hi Bruce

The upload folder is still full.  Can't send anything.

Keith

[Keith]

Hi Bruce

In the process of creating a cut down app and dct I found out something new.  MY new dct has only the three related files (Customers-Bookings-BookedPets) and the Wizard created the application without errors.  But then I deleted the updateBookedPets procedure and asked the Wizard to just add that and got the error.

So, Here is the app with the procedure 'ToDo' and if you use the Form Wizard you should get the same result.

Cheers

Keith

[attachment deleted by admin]

[Keith]

Hi Bruce

This may have something to do with the 'key depth' i.e. that there are three components in the BookedPets key in the relationship with Bookings.

I created a new key on BookedPets - just on one field, BookingNumber and related with Bookings via that key and the Wizard worked fine.

Keith

[Keith]

Update.  The new build of C9.1 encountered the same type of problem as described here but with a different file - again a multi-component key.  But it gave a 'graceful' option and a description of what it thought the error was viz:

Unhandled exception
Exception thrown:
System.InvalidOperationException: Form that is already visible cannot be displayed as a modal dialog box. Set the form's visible property to false before calling showDialog.
   at System.Windows.Forms.Control.EndInvoke(IAsyncResult asyncResult)

Keith

[Bruce]

thanks for the example Keith.
it wasn't to do with the key, it was something else, but I've fixed it in 8.27.

cheers
Bruce

[Keith]

Thanks Bruce.  Look forward to 8.27.

Keith