

It is sufficient in D2009 to write 'ioutils' in uses as the name of the. Kai Inge, I think Jeff forgot that you are on D2009. > but the dcu is gone or damaged, so I can't use it. > annoying knowing the System.IOUtils is there, > I managed the task of coding with other code, but think it's a bit > Yes, when one way don't work, I try the other, though neither works in Spend that pile of money on my hobby, is holding me back :-) The problem with giving my dear wife a qualified reason why I should Upgrading would have solve the challenge, but still I think that XE5 is I managed the task of coding with other code, but think it's a bitĪnnoying knowing the System.IOUtils is there,īut the dcu is gone or damaged, so I can't use it.

Yes, when one way don't work, I try the other, though neither works in > only really a short term fix until you switch everything over, new > System part to the Unit Scope Names in your project options (this is > introduced you with have to fully qualify the unit name or add the > It should be written as System.IOUtils. > Have also tried System.IOUtils, TSystem.IOUtils, to no avail. > satisfy the compiler, as it don't find the DCU.) What more can I do than write it into the uses list? (which do not
