ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> IN-A totally broken
http://www.istechforum.com/YaBB.pl?num=1237808099

Message started by kkmfg on 03/23/09 at 04:34:59

Title: IN-A totally broken
Post by kkmfg on 03/23/09 at 04:34:59

To be clear I think this is a problem with our data or installation and not a real evo bug.

Thursday or friday we started having real trouble with IN-A (the T7 version. Newest evo update). It says:

You have a DEFINE command without any field names. The popup has "line 2215" in it's title.

This is happening on any machine and rebooting the machines doesn't seem to help. I've even tried rebooting the server.

For what it's worth, the other versions of IN-A work fine.

Title: Re: IN-A totally broken
Post by NovaZyg on 03/23/09 at 09:02:04

I believe someone in your CO was trying the new UDF fields and did not finish them correctly.

We are trying to tighten the post save validation to erase any incorrectly set up UDF's but that version is not out yet..

What the UDF's do is to use a Table to define fields that get compiled at runtime in IN-A and IN-B.

Are you getting the same errors in IN-B too?

if so, use SM-P-E to edit the user defined fields.. if you are not useing UDF's then that table should be blank.

Title: Re: IN-A totally broken
Post by kkmfg on 03/23/09 at 11:30:53

I'm pretty sure that nobody would have messed with the UDF stuff but I suppose never say never. I looked at that SM-P-E and it was strange. The first time I brought it up it had three fields all numbered zero (I think) and all blank. I tried to delete one and it crashed. I ran it again. It showed four fields all of which had sequential #'s, field names, etc. They looked really generic. I tried to delete one and it crashed. I tried again and it crashed. So I tried IN-A again and it works fine. I can't explain it but so long as it's working I'll take it.

Title: Re: IN-A totally broken
Post by NovaZyg on 03/23/09 at 11:38:13

the generic ones are the defaults.. if you run it and there are none setup it adds in the generic ones. But if you just exit it removes the generic ones thinking there was nothing really to save. But as you said you had some stuff in yours.. that was what was causing the Error. I am working on adding Validation code to our Grid editing ( something that sounds easy, but really isn't ) All our grids are generated by a Library and Edit currently is a switch (on/off) I need to find some way to add validation code to fields in the grids that are stored in tables that the user can modify (SU-A)... :-/