Oops missed the alternative idea.
The project that will replace the current Access front end based system
is being written in C#.
My only problems at present are some incompatibility issues with OR
mapping classes and UI controls.
What I find irritating is while a Dataset will perform flawlessly with
the UI controls (those that data bound) but when I bind some entity
collections to the UI controls either directly or via a binding source I
have issues in some instances. At least with Access (and I strongly
dislike Access) this situation does not arise. Where I have such a
problem, I have to convert the entity collection to a Dataset and when I
have finished, reverse this. So far the issues are related only with
tables that have a self join. Fortunately I only have two tables of this
type in the database.
Regards Peter.
On 9/03/2010 6:34 AM, Arjang Assadi wrote:
Alternative idea : Throw away the Access front end and do it all C#,
call it the next version of the software.
