Hi everybody,

Here is my problem today. Working on Mac OS 8.6 and FM 5.5. Actually I solved part of the problem while making this post, but I do not really undersand the process, so I keep posting the following.

I have a Product File that holds 20,000 records in it.

This product file holds some records as :

Manufacturer

Product Category

Collection

Product Designation

Price.

A Manufacturer have many collections, A collection can hold many categories.

I wanted the user to filter the Product File choosing one of 2 different methods :

1st method : Choose a Manufacturer from list, then choose all categories attached to this manufacturer, then choose a collection according to both first selections.

2nd method : Choose a Manufacture from list, then choose a Collection attached to this manufacturers, then choose a category according to both first selections

I therefore created :

3 global fields :

- g_Manufacturer

- g_Category

- g_Collection

6 calc fields

- c_ManufacturerAndCategory = t_Manufacturer & "-" & t_Category

- c_GManufacturerAndCategory = g_Manufacturer & "-" & g_Category

- c_ManufacturerAndCollection = t_Manufacturer & "-" & t_Collection

- c_GManufacturerAndCollection = g_Manufacturer & "-" & g_Collection

- c_Concanatedtotal = t_Manufacturer & "-" & t_Collection & "-" & t_Category

- c_GConcanatedtotal = g_Manufacturer & "-" & g_Collection & "-" & g_Category

4 relationships :

- SelfjoinOnManufacturers ----> g_Manufacturer::t_Manufacturer

- SeljoinOnCategoryPerManufacturer ---> c_GManufacturerAndCategory::c_ManufacturerAndCategory

- SelfjoinOnManufacturerCollection ---> c_GManufacturerAndCollection:: c_ManufacturerAndCollection

- SelfjoinOnConcanates --->c_GConcanatedtotal :: c_Concanatedtotal

5 Value Lists :

- Manufacturer List = Use records from Product file (t_Manufacturer)

- Category List 1st method = Use related records ::SelfjoinOnManufacturers (t_Category)

- Category List 2nd method = Use related records ::SelfjoinOnManufacturerCollection (t_Category)

- Collection List 1st method = Use related records ::SeljoinOnCategoryPerManufacturer (t_Colletion)

- Collection List 2ndmethod = Use related records ::SelfjoinOnManufacturers (t_Colletion)

I then attached Manufacturer List to g_Manufacturer, Category List 1st method to g_Category and Collection List 1st method to g_Collection, and draw 2 portals showing list of items from related records :

- Portal 1 : SeljoinOnCategoryPerManufacturer

- Portal 2 : SelfjoinOnConcanates

Having these 2 portals was'nt useful as only Portal 2 shows accurate results from the Filtering process. But I didn't thought of this happening. FM always quits at last step of filtering process when Portal 1 is on the layout.

I do have the same when processing the filter with second method.

Can anyone give an answer to this odd (at least for me) behaviour.

You might try moving to a different platform and see if the crashing stops. Chances are something is wrong and it will be come clear if you can review the last filtering result without FM crashing. Off hand nothing looks out of place. Just make sure all the fields in each portal are fields from the proper relationships. You might also try removing elements from the first portal to narrow down which object is causing the crash. Sometimes objects become corrupt. You might try recreating the elements of the first portal.

-bd

Thanks for the imput.

I completely reset the portals. Everything is working fine now, even with as many portals on Layout. Actually there were no objects, only three fields in it for description, size and prices.

Prices may have been somehow a little "out" of the row. Could it be the reason for this Type 2 error message ?

I thought this kind of messages on Mac were linked to Memory incident. That's why I had first looked for a kind of circular relationship...

As this is just a test file, I just hope I would not discover another reason when the new database will be over ...

Nothing on a layout, script, field, etc. should crash FM. All errors SHOULD be trapped (oh, well). Type 2 is supposed to be a memory error, but categorization isn't all that exact.

-bd