Hi,

I have a feeling that I am trying to do something that may not be able to be done, but want to run it by someone who has more than 10 hours of programming time (unlike me). I am using SLX 7.5.0.1 LAN. On the Contact Detail form I have created a TabControl and have placed a ComboBox inside of it. I have the ComboBox populated with 9 items. I also have 7 checkboxes in the Tabcontrol.

My desire is to have a user select one of the items in the Combobox, as well as be able to check none,some or all of the checkboxes. This will then write to a new table I have created. My new table contains a ContactID column, a ProdNotificationID column (identity increments), a column that the item from the Combo will write to. Lastly it has 7 columns (booleans) that map to my checkboxes.

It works fine ONE TIME. But if I change the item in the Combobox and hit 'Save' rather then inserting a new record for that Contact, it just updates the previous record.

So far I have tried remaking the table in the DataBase manager and using 'Many to One' relationship with the Contact table. I've tried having no relation to the contact table. I've tried using the 'auto increment' on the ID column created when building the table in Database Manager. I think I am missing something fundamental in SalesLogix and programming in general. Unfortunately I dont even know where to begin to try and acquire that knowledge in a timeframe suitable for this project.

Any help, advice, heckling would be most appreciated!

Thank you

It can definitely e done - but, there are various things you can/need to do. Without getting into the complexities of it (sorry!) - you will need to code the test for whether the combo box (which identifies the entry) exists already for the table (for this contact) and then launch code that either updates or inserts. You can't rely on SLX doing this as it what you are trying to do is outside of it's remit of the normal update/insert on grid style idea. 

So, pyseudo would be:

- On button press

- Find the combo box item, locate the row in the custom table for this combo box data and the contactid. If it exists, then it's an update, if not - insert

- The table should be 1:M off of Contact (you could go with None but then you'd have to find the data at the form open to populate it - you can have SLX do that instead if you are 1:M off of contact)

It worked! Thank you for the ideas Mike. I ended up getting some assistance from my SLX mentor (guy I took over for). I am continuosly amazed at how flexible SalesLogix is.

Typically, if you can imagine it - it can be done! Sometimes, however, you just need to go outside of the norm to make it do what you need !