I'm documenting this issue in hopes of helping others who may come across the same problem. I'm converting my app to use MYSQL. During testing, I've found that I've lost my search highlighting that should be happening in my grids when I use the quick search feature. My search results would be correct, but the search value wasn't italicized in my grid as it had been before. After spending much time and going down the wrong path looking at CSS, I found the problem to be in the fields to search property for quick search.
1. Example of property value in dbf version:
Field(s) to Search: Firstname,Lastname,Compname1,Typedesc,Address1,Address2,City,State,Postalcode
Note: Some of these fields were hidden fields on the grid so they would be searchable but not take up real estate. This didn't work with the new version. It returned a sql error.
2. Example in MYSQL version when using the button to pop up a list of available fields and select fields from there:
Field(s) to Search: contacts.FIRSTNAME,contacts.LASTNAME,contacts.ADDRESS1,contacts.ADDRESS2,contacts.CITY,contacts.STATE,contacts.POSTALCODE,conttypes.TYPEDESC,company.COMPNAME
3. Example in MYSQL version that actually provided the results I wanted:
Field(s) to Search: Firstname,Lastname,COMPNAME,Typedesc,contacts.Address1,contacts.Address2,contacts.City,contacts.State,Contacts.Postalcode
I assumed when using the popup to select my fields to search that it was working like it did before. I don't think that's the case. I think it was clearly searching the database and not the grid values. They should be the same except that it resulted in my grid values not being highlighted in the results. If I had not used the pop up box to select search fields, I would've been O.K. typing fields from the grid as they appear in the fields section.
So, don't use the popup box to select fields for quick search unless you don't care about search highlighting. If you type in some fields and then use the popup, it replaces your text you've already entered.
Hope this saves someone some time!
Lisa
1. Example of property value in dbf version:
Field(s) to Search: Firstname,Lastname,Compname1,Typedesc,Address1,Address2,City,State,Postalcode
Note: Some of these fields were hidden fields on the grid so they would be searchable but not take up real estate. This didn't work with the new version. It returned a sql error.
2. Example in MYSQL version when using the button to pop up a list of available fields and select fields from there:
Field(s) to Search: contacts.FIRSTNAME,contacts.LASTNAME,contacts.ADDRESS1,contacts.ADDRESS2,contacts.CITY,contacts.STATE,contacts.POSTALCODE,conttypes.TYPEDESC,company.COMPNAME
3. Example in MYSQL version that actually provided the results I wanted:
Field(s) to Search: Firstname,Lastname,COMPNAME,Typedesc,contacts.Address1,contacts.Address2,contacts.City,contacts.State,Contacts.Postalcode
I assumed when using the popup to select my fields to search that it was working like it did before. I don't think that's the case. I think it was clearly searching the database and not the grid values. They should be the same except that it resulted in my grid values not being highlighted in the results. If I had not used the pop up box to select search fields, I would've been O.K. typing fields from the grid as they appear in the fields section.
So, don't use the popup box to select fields for quick search unless you don't care about search highlighting. If you type in some fields and then use the popup, it replaces your text you've already entered.
Hope this saves someone some time!
Lisa
Comment