11/27/2024 4:23:44 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
Manage Addresses broken
Posted: 13 Feb 07 7:25 AM
|
fiogf49gjkf0d Looking into our db that has been around for many years, I am trying to test replacing a Legacy Contact Detail form with one from the current version (6.2).
Working with the current Contact Detail form, when you launch the Manage Alternate Addresses form using the cmdAddress button, the SQL that is executed includes the field A1.ADDRESSES. An error is thrown that the column name "ADDRESSES" is invalid.
Taking a look in Calculated Fields, there is a field with the Alias "ADDRESSES" comprised of Contact.Address.Address1 and Contact.Address.Address2.
Is the Alias permitted in SQL statements? Can anyone suggest a reason why the Alias isn't recognized in the SQL? How does this break?
This also doesn't work in Execute SQL.
Thanks!
Rick |
|
|
|
Re: Manage Addresses broken
Posted: 13 Feb 07 1:03 PM
|
fiogf49gjkf0d Rick,
The calculated fields will only work when SQL is executed through the OLE DB. The OLE DB provider actually returns the "calculated" fields.
HTH,
Ron |
|
|
|
Re: Manage Addresses broken
Posted: 13 Feb 07 1:18 PM
|
fiogf49gjkf0d Hi Ron,
Yes, thanks, this I know! Using Execute SQL from within Administrator (and thus via the provider), I get the same error... I had thought perhaps that I had NULL values that were causing the problem (trying to combine Address1 with a NULL in Address2), but I checked this on addresses that have values in both and still get the error.
Sleuthing further, I found that the DataGrid in the Manage New Address form does not appear to use the field ADDRESSES. The ADDRESSES field is only used in the Manage Alternate Addresses form.
Rick
If anyone has a moment to test, just curious if this SQL works in other dbs (inserted TOP 10, removed :BindID, otherwise the same):
SELECT TOP 10 A1.ADDRESSID, A1.ISPRIMARY, A1.ISMAILING, A1.DESCRIPTION, A1.SALUTATION, A1.ADDRESSES, A1.CITYSTZIP, A1.COUNTRY, A1.ENTITYID, A1.CITY, A1.STATE, A1.POSTALCODE FROM ADDRESS A1 ORDER BY A1.DESCRIPTION ASC |
|
|
|
Re: Manage Addresses broken
Posted: 14 Feb 07 8:40 AM
|
fiogf49gjkf0d All,
I know you've been on the edge of your seats wanting to know how this turns out...
We did some experimentation and determined that the problem existed with the Calculated Field called ADDRESSES. Somewhere in our database's lifetime, the Calculated Field was set up with the Base Table as CONTACT and the string calculation as Contact.Address.Address1 Contact.Address.Address2 (btw, what's up with that nomenclature - no "+" or "&", just put two strings next to each other...). By deleting this instance of the Calculated Field, and then creating it anew with the Base Table as Address, and the calculation as Address.Address1 Address.Address2, everything works.
Now that this mystery has been solved I'm sure we'll all sleep better tonite... |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|