This is my first project using the UltraGanttView so I'm still learning.
I've got my database tables for Projects and Tasks set up. Not sure I have the field values accurate. I saw in the help where it lists the fields but not types or sizes.
When I use the DataBinding sample and display tasks, it shows fine. I can modify the tasks and then save back to this table and it so far it seems to save all fields except the Resources. The resource will display on screen, then I save. If i restart the project the resource is not there now where all other changed properties are. I can't view the values in AllProperties in sql since it is binary.
Should the AllProperties field be a different type or be larger? Also, am I supposed to be populating the Resources box in some way for it to match up? If so, how to I load the possible Resources?
Thanks for any help.
If someone has info on how big the AllProperties field should be, I can still use that but I found my answer to the Resources issue.
I have to set the available resources as part of the ultraCalendarInfo object Owners property. After that, the names show up in the the Resources list and it will select the ones I saved.
Did you manage to get the resource info from your database to be recognised by the task or saved it as part of the allproperties?
My requirement is slightly different as the resource details including their duration,expense etc on tasks is needed in other part of the application for billing and project analysis, the data has to be in a readable and queryable format.
I think I will have to create my own custom Task Info dialog as the built-in dialog is too rigid. I did notice there was no option to limit to list in the resource combo, which means you may have to create your own dialog if you want that option.
Yes. I have a SQL table that contains our Available Resources. When loading the application, I am loading the Owners property of the ultraCalendarInfo object with my resource names.
The user can then select one of those names, it will save in the AllProperties field and display back correctly later.
The thing I did not solve is that it will still let the user type in a name which appears to save but won't display back. Since this app I'm developing is being used by a limited number of users, we just went with user training to explain that they needed to select from the list and not type in a new item.