On Thu, Dec 02, 2004 at 09:47:42PM -0600, Ron Johnson wrote: > Thus, an Access replacement should do all those things, but w/o > being buggy. Certainly you could have figured that out
Since my data is stored in XML, I can do everything and more I can do with Access queries and reports using xsltproc to select bits and present it. My UI component is sort of a "universal form" -- it has checkboxes and in particular comboboxes for lookup tables. All that stuff is done automatically. It doesn't support custom code-behind or addins, Access has that. But mine supports replication and merging. You can't use my app to make a order entry application, but I do some pretty good tricks with it. I download my bank statements and view them in the UI component. I view diffs in it. I manage my video collection, and all my contacts, todo list, bills, and account info in it. Since it's a generic UI component I use it as the "Tools|Options" dialog in a few custom apps. It's more of a workalike. I don't care if everybody else thinks it sucks. The things it doesn't do should be done using a proper RDBMS and a real frontend. It does one thing and does it well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
