Hi Frank,

I have attached a sample of mine. Please let me know if my sample works on your side perfectly or not.

If my sample did not met your scenario please change my sample until the issue can be replicated and send it back to me again therefore I can investigate more further regarding your issue.

Hope this helps.

Regards,
Niven.

Hi Naaz,

Based on your screenshot, this is not an issue. All the listed fields in DataBinding was the main requirements for WebScheduler to work. You need to set all the fields exatcly as you have watched on the video.

As to create your own field and want to implement it on your WebScheduler, you can refer to our WebScheduler samples, EventOrganizer.aspx page.

You need to add it manually inside the events windows. As you see the DataSet for EventOrganizer, we add a custom field, Notes and Attendees. And the way how to implement it, you can see the Javascript snippet code.

Hope this helps.

Thank you and have a nice day.

Regards,
Niven

Hi Naz,

Thanks for downloading and taken an interest on our product.

Could you please more specific on the details, which property window that are not appearing? Did you mean the Properties windows when pressed the F4 button or something else? If you don't mind, can you provide me a screenshots of it so I can investigate further which scenario you have been dealt with.

Thank you and have a nice weekend.

Regards,
Niven.

Hi Shawn,

I apologize for the misunderstanding. I think I am getting lost and want to clear the questions first.

So you want to access the new row but you dont want your users to add something within the new row field? If you want this scenario, I can suggest you to handle this scenario on OnRowSelect client-side event and set the validation if the ColumnType is new row then set to no edit type.

And If below is not the scenario you wanted, have you tried my previous snippet code that hide the new row? Even it is hidden, you can still adding a new row. Only the style was hidden you still can access it.

Thank you and have a nice day.

Once again, I apologize for my misunderstanding.

Regards,
Niven.

Hi Bill,

I have looked again at my sample and its doing fine on my side.

I have attached my simple sample, could you please try the sample on your side? If you don't mind, could you please send me a sample of your application?

I will investigate it more further based on your sample.

On my sample, please run the first try without the Topmost property called.

uXDialogBox1.Topmost = true;

and on the second try please run in with the UXDialogBox1's Topmost property called.

Thank you and have a nice day.

Regards,
Niven.