Hi Trent,I am evaluating StrataFrame right now and found this post which interests me since I have a scheduling intensive VFP application for health care rehabilitation providers and I am considering a move to .NET. My first evaluation is using StrataFrame and my second will be interface controls like Infragistics.
For most scheduling views, my current VFP application uses a very complex set of grid objects to display time/resource rows and columns and it exceptionally fast and efficient. While it was extremely complex getting everything to work, it looks great, is lightening fast, and bullet proof running over a WAN with over 200 users. My decision to custom build was simply because the 3rd party market controls like DBI were either too specific (wareshouse/point of sale) or contained bloat as you referenced in your original post.
I am curious to know if the developers at StrataFrame evaluated any scheduling controls and if the main decision factor was the bloat of those controls or the lack of customization? Additionally, what was your approach to building a custom control----was it using building blocks from existing .NET/Strataframe objects or did you build it from scratch?
Thanks,
Bob