Problem with OLEDBAccess.CreateUniqueFieldName
Posted: Tue 08 Jun 2010 11:14
Hi,
I've a problem with queries where no fieldname was specified for calculated fields. With latest update of SDAC (480_058) you changed the CreateUniqueFieldName adding two '_' in front of the name (ex. __COLUMN1). Since in reports and queries this fields are accessed through fieldByName('COLUMNxx') this part of code now raises errors. Was there a reason to change this behaviour? Would it be possibile to solve this through a property on the TMSQuery (something like UniqueFieldNamePrefix)? In the meantime I will change the OLEDBAccess to return to previous behavior, otherwise I've problems with my customers.
Best regards
Toni Santa
I've a problem with queries where no fieldname was specified for calculated fields. With latest update of SDAC (480_058) you changed the CreateUniqueFieldName adding two '_' in front of the name (ex. __COLUMN1). Since in reports and queries this fields are accessed through fieldByName('COLUMNxx') this part of code now raises errors. Was there a reason to change this behaviour? Would it be possibile to solve this through a property on the TMSQuery (something like UniqueFieldNamePrefix)? In the meantime I will change the OLEDBAccess to return to previous behavior, otherwise I've problems with my customers.
Best regards
Toni Santa