here's a mess that cost me a whole day..
when a field in an sql db is variable format,
FIELD/AnV,
and you don't perhaps know this in advance.
and you
TABLE FILE ..
PRINT FIELD ..
ON TABLE HOLD...
END
then later
TABLE FILE HOLD
PRINT FIELD ..
eda crashes and not just the agent...the whole eda dies an ugly death.
Repeated this , oh, 50 times yesterday.
Till i figured it out, and edited all the /AnV to /An before reading the sql.
Head stopped hurting now, but brickwall has major dent

Should I have known something in advance that I didn't ?

Susannah,

Wasn't there some kind of restriction that the AnV field had to be the last one in a TABLE FILE, and that you can have only one? I can't find the documentation on this though.

S.

Obviously you are a bit annoyed and may have this as the last thing in the world that you want to do, but could you post the precise code that killed eda since I have done what you describe many times without this behaviour.

When you say it killed EDA do you mean you had to reboot the entire server to get it working again?

Regards

John

Starting somewhere in release 7, when you generated the masters for relational engines, the alpha formats were changed to variable. I think that is because the real relational column is defined as a VARCHAR.

That cause quite a bit of havoc at our site as well. Our resolution was to put the following in the edasprof.prf where the connections are placed (and we have lots as you can see below):

ENGINE engine SET VARCHAR OFF

Then regen the master.

I don't know if you should have known that in advance. We just stumbled across it as well though we didn't have server crashes. We had failed joins.

I hope your head feels better.

Brilliant, Ginny. thanks.
Yes John, had to reboot the whole puppy.
Frankie, that sounds reasonable...

This message has been edited. Last edited by: susannah,