arcusfil_sql.cus_origin 2

[longbows]

We want to track how we get new customers and noticed a field called cus_origin in the customer table. Does anyone know of a reason we shouldn't add it to the customer maintenance form and use it. It's only one character and currently it's NULL in all of our customer records.

 

[dgillz]

The only reason not to use this is, if Exact is not already using this field, they surely are planning to. So at some point in time whatever you put there is likely to be overridden.

Use a user defined field, thats what they are there for.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

http://www.gainfocus.biz

 

[abaldwin]

Good point Don, Another reason to use the user_def_fld_1 ...5 is that when you do an upgrade say to ES you are not guaranteed that a non-used field is going to be converted over and you may have problems getting that data into the ES customer information tables.


Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[longbows]

I was reluctant to use one of those fields because they're 30 characters and 1 character would work nicely. I didn't want to get in a situation where I needed that field later and then had to use it for multiple purposes where I would then have to parse it before interrogating it.
But your point is well taken. Thanks for the advice.

 

[abaldwin]

What version of Macola and the backend are you using?

Pervasive or SQL? As a general rule I would not use a non-user defined field for ANYTHING other than what Macola uses it for. If macola does not appear to use it I still consider it off limits since you are never really sure what the intent of a field is.



Andy Baldwin

"Testing is the most overlooked programming language on the books!

 

[longbows]

7.6.300a - SQL
No, you're right. Not knowing their intentions it's best to leave it alone. I just thought since it was called cus_origin maybe it had been used for something like what I wanted and was no longer really used, or used in a way that wouldn't affect us.
Actually I may use the first or last character of the salesman code to identify it and use the other 2 to uniquely id the salesman.

 

[abaldwin]

Since you are SQL I would simply build a table holding the different mailings, marketing campaigns, and other points of origin and use that table as a feeder table for a flex app to populate a user defined field. Or build another table to relate the customer to their origin.

SQL gives you some serious options when it comes to data that macola can not handle.



Andy Baldwin

"Testing is the most overlooked programming language on the books!