... or so it would seem. Discontinued with the release of D2 but still haunting unit uses clauses everywhere.
I just recently tracked down and fixed an error in a module that was compiling fine but causing the Code Completion and Code Parameters IDE features to fail once it had.
Tuesday, April 12, 2011
Friday, April 1, 2011
I have a requirement for several simple database centric look-up tables in one of my projects. They are no more complex than name-value pairs [EA-Each, CT-Carton, ... ] that get stored in the database and are fully editable by the users. I needed to find a way around the tiOPF [the OPF of choice] default of using GUID OID values for any object you plan to persist because, to my mind, there is something seriously wrong with storing “6FFC3175-37CD-4682-A599-EF6B86E1F397” over and over to represent “Each” where “EA” is more than up to performing the task.