I changed Index 1 on one of my custom tables. All is well. I now have trouble with a session that was created with the original index.

When I run the session alone - I can find any record I want, and the data is sorted on the new key. When I zoom to the session from another, and use query.extension to select the correct customer number (from other session input), it fails.

Any hints? I know I don't have a lot of info here. I can't imagine that I would have to regenerate the session - would I?

D

Does it fail by not returning the correct customer? What happens when you zoom to this session (in debug mode) from the other session? I am curious if the other session has everything set correctly for the new index. Running it in debug might provide a little more info for the more knowledgable experts than me.

Mark

I suposse both are custom sessions.

Have you checked your selects (refered to that table) in the second session you mentioned?

Maybe you have to compile again session script.

Let us Know.

I was getting a reference error on the item group table, tcmcs023. On three fields of my key--citg, ctyp and comp, I have the table referenced to the appropriate master tables.

Like I said, when I enter the session without the customer number input - it was fine. I'm using the reference tables to display the correct descriptions on my form for item group, product type and company (at least in this session).

So...I removed the descriptions from the form...then FINE!

I would think I had a table problem, but it displays fine without the input.

Thanks for the help...I tend to get dangerously creative sometimes. Yes, it's custom. I really just needed to know if changing index1 should affect sessions - and I think the answer is no.

D

I figured it out - I had actually moved my table def from my PROD system to my TEST system, so I created RDD on my 'td' table in TEST.

I needed to run a create RDD on all the linked tables (tcmcs023, tcmcs015, tccom010, tccom000) in TEST.

Can someone verify that this is correct?

1) Change table def - run convert RDD wide open and it will pick up all the linked table changes.

2) Import table def - run create RDD on new table AND all linked tables.

Thanks for your patience everyone!!

D

It seems to me that I used to be able to just run Create Runtime Data Dictionary on the imported table and it would take care of the references in the linked table(s) as well. However, as of late, my experience is similar to yours -- you must use CRDD for all of the referenced tables as well. I could be wrong, but I never remember it being such a big hassle before.

D said:
Thanks for the help...I tend to get dangerously creative sometimes. Yes, it's custom. I really just needed to know if changing index1 should affect sessions - and I think the answer is no.

Just noticed this while I was checking Ed's post. Changing index1 can cause sessions to go "kablooey" (my own technical term), but not always. We ran into this when Baan sent us a patch and index1 changed on one of the tables. One of our custimizations started returning the wrong records.

I also never run create RDD wide open, just my preference. I never want to convert something someone else may be working on.

Glad you found your fix!

Mark