Lookups going "blind" and not looking up?

[Leb i Sol]

Hello People!

Sorry for another post about looksup but I am really confused here... I have never seen this and perhaps some of you have and can help me.

Here is a little intro on related files:

ITEMS.fp5----------------------------------------------

WS_ID - auto enter serial

ItemID - text (eg. cx-1001)

relationship:

ITEMS_LINEITEMS WS_ID= ::WS_ID ITEMS

________________________________________________________

LINEITEMS.fp5------------------------------------------

ItemID - lookup

relationship:

LINEITEMS_ITEMS WS_ID= ::WS_ID LINEITEM

_______________________________________________________

soo...all this is great and working...the portals and all Other lookups from other files...but I noticed that (working from Items file) only 4-5 first records (ItemIDs) added are actually being "looked up" in the LineItem file?:?

Also, I tryed to set (in LineItem file) field ItemID to be auto-entered calculated value (=LINEITEMS_ITEMS::ItemID) instead of a look up but no luck?!!

what can it possibly be that is stopping a lookup from looking up after 4-5 records added?

Thank you all for any help!

p.s. repeatng my words IS still a help..sometimes I don't hear myself until someone repeats it :

[Ugo DI LUCA]

I had this kind of issue once and solved it with a very small arrangement.

The thread was called "Lookup not looking up" I think.

Now, from what you said about your calc not working, it seems to me that this could be another issue. Make sure at first that your relationships are correct and that triggreing a Re-lookup is working.

If it does, then I think you might have a look at the threa mentionned above.

[Leb i Sol]

OK, I narrowed it down to this and perhaps my post should be changed:

1st Portal Entry will not trigger the Lookup but any other portal row (entry) WILL??!!

____________________________________

Ugo:

"triggreing a Re-lookup is working."

Unfortunately it does NOT...if I run it I get the error sayign that there is no field ("ItemID") using a lookup....but obiosly it is...?

could this be a relationship issue?

thank you Ugo...and who ever joins on the topic!

[Leb i Sol]

hello there!

Well, here is my answer to my own question:

LINEITEMS.fp5------------------------------------------

ItemID - lookup

relationship:

LINEITEMS_ITEMS WS_ID= ::WS_ID LINEITEM

=======================================================

instead of using a lookup for the ItemID I set the ItemID to be a

Calcualtion Unsored,=LINEITEMS_ITEMS::ItemID

and this works a LOT better than a pure lookup!

the only problem I see with a calculation is that is can not be validated without any other fileds involvement.

BTW Ugo --> I have not been able to find that post again

Anyhow...if any of you guys see my approcah as a potential problem please do post your opinion!

Thank you all!

[Ugo DI LUCA]

Zila,

Here's the thread I was refearing to :

link

Choosing from a lookup or a calculation depends upon the data that is to be "imported".

You'd probably calculate a Product Name or description, but you won't use a calculation for price, because all your old prices and old invoices would change.

[Leb i Sol]

thanx Ugo!

I realized what was the mistake...as u can see by the blob of my posts

ItemID is (in this case) manually entered and it was a mix of txt and numbers (ABBC-1234) and I belive that dashes were not processed correctly and also both fields need to be a text. Somtimes the concept of having 2 text fileds "being calculated" is strange way of looking things....especially if you havemy level of expreince with FM......

u know what they say... "Live & Learn"

Thanx_