General information
Category:
The Mere Mortals .NET Framework
Title:
Beware changing business object name, case sensitive
If you suddenly can't get any database actions to work it might be because it has something to do with case sensitivity.
I decided to do a number of changes to my project, which is pretty hefty, including prettying up the names so they look better.
I happened to change purhead, the name of my Purchasing application's header business object, to PurHead.
After that none of my database actions, New, Update, etc. would work any more or I should say nothing appeared in my controls. I thought that Basic was case insensitive, so didn't even think of that as a problem, also since I made name changes in my code from purhead to PurHead, and we all know that source code is case insensitive. It took a week for me to find that the problem was each control's BindingSource.
When I picked each control's (38 of them on one tab page alone) BindingSource from purhead to the new name, PurHead, it all worked again.
Bugger.
CU
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only