Adding field to database -- Bad Idea?

[ctwilliams]

We are using both of our USRDEF fields in the Customer Master table, however we need one more field (bit) to put "PO Required?" info into. (Eg. for Customer # 123 if a PO is required then put a 1 in this field, otherwise put a 0.)

I know how to add the field to the SQL Server database table using Enterprise Mgr and then add it to the form using VBA, but is this a good idea? What will happen when we upgrade GP in the future -- will my custom field get nixed? Are there some USERDEF fields in a GP table elsewhere that I can use instead?

 

[curtman]

GP exposes an object called the DUOS or Dynamics User Object Store. There is some good documentation in the VBA Developers Guide which can be found in the Dynamics\Documentation\Manuals folder.

I have used this on several occasion to do similar things.

Curtis