I am referring to the code posted in reply #20.
Get rid of the "semi-circular" unit reference situation: unit uMain has uParser in its "implementation uses",
Yes I call uParser from uMain in a Modal call passing a record with a filename and path.
implementation
uses uParser;
As far as I know I have to have this in order to call it Modal and pass the record.
and uParser has uMain in its "interface uses" at all.
Normally this should still compile, but I don't know what cody etc is doing if there's an error. Better to avoid this situation in the first place: You have a general declaration unit, uParser. Move the declaration of TDataRecord from uMain to uParser, remove uMail from uParser. Checked if the renaming actions still occur.
The way it is it compiles and dosn't complain.
I'll make the changes in a test and see if I can still pass the information from uMain to uParser and still pass the required information. ie the file for uParser to open.
What I'm trying to accomplish is the following.
A main form which can call two forms Modal and use a utils unit
1 form will parse data and use a utils unit
1 form will setup inifile info.
Main form needs to pass a record to uParser and uConfig.
What you suggesting I don't think will accomplish the requirements.