Tom:  Glad my suggestion prompted your solution!   But I just tried 
something
else here.   I created a temp table, created a form based on it, and in the 
"on
before design eep", I dropped the temp table then put the temp table 
definition 
in there.  Saved the form.  Then I went into the "on before design" and 
purposely 
made a change to the table definition that would make the table not work 
(left off a datatype).  Tried to bring up the form and of course it 
wouldn't come up.   
I did an "edit all from sys_forms3", edited sys_data and easily found the 
code 
at the beginning.  Changed the code to make it correct, saved it, and now 
the 
form comes up.  So in your case you didn't need to bother adding in the old 
names;
you could have gone into sys_forms3 and just modify the code.

Karen

 
> Razzak and Karen,
> You got me on the right path. Went to an older working copy of the 
> report from 3 months ago. Looked at the old view and the current problem 
> view. I had changed one letter in three column names to stay more 
> consistent with a naming system that just developed. Makes much easier 
> reading to me. The name changes were great for other reports, except I 
> forgot to adjust this one report, so I basically adapted Karen's idea. 
> Inserted the old names into the current table and up pops the trouble 
> report in designer. Changed the report fields to the correct names, 
> moved the data to the new columns, deleted the trouble columns, and it 
> now runs like it should. Took maybe 30 minutes. The other reports all 
> work. Than you for the brain kick.
> 
> Tom Frederick

Reply via email to