A
a
I am about to write an application that is very much a Database GUI, with
entry forms and reports. Given the number of posts with issues in VB.NET
databinding, are there any good reasons to not use MSAccess as a front end
to an SQL Server DB? I prefer VB.NET, but the ease of Access is very
enticing. Every time I have done databinding in VB.NET, I have had some
issue or another.
Put another way, are there any concepts/practices I could implement to make
VB.NET a better choice?
Thanks for any ideas.
entry forms and reports. Given the number of posts with issues in VB.NET
databinding, are there any good reasons to not use MSAccess as a front end
to an SQL Server DB? I prefer VB.NET, but the ease of Access is very
enticing. Every time I have done databinding in VB.NET, I have had some
issue or another.
Put another way, are there any concepts/practices I could implement to make
VB.NET a better choice?
Thanks for any ideas.