>Really appreciate your quick response. We are on SPS08 Rivison 85.
My app is from SPS 09(Rev90), so it wont' run directly on SPS 08. I used newer libraries. Your welcome to study though. The core concepts are certainly doable on older releases as well.
https://dl.dropboxusercontent.com/u/643382/HCO_XSOPEN_TBL_CONV.tgz
>What is the benefit of HDB tables over tables created using SQL. The only reason I am planning to use this is for version control and change management ?
As you said version control and change management. Also the ability to transport the content via Delivery Unit. As of SPS 09 we also have some great lifecycle management features. If you change the key structure, column order, data types, etc - upon activation we will export the data and re-import it into the table. Without HDBDD you have to do this yourself. Don't forget that we also have features SQL doesn't - like Associations. And now libraries like XSDS to use the entity and associations directly. In the near future we will generate OData services directly from the HDBDD definitions without the need for the XSODATA object.
>Is there any way to enable version control for catalog objects ?
No.
>Is there any way to view the change_id associated with an Object ?
Not in the standard tools. You could maybe write your own query for this. The stardard tools only allow you search by status, change id, contributor, status, and release date.
>Later on when other users are doing change on same object then they are not able to find change_id under which object is tracked.
If the object is still associated with an open change ID, anything they do should be added to that change without them having to choose the specific one.