MSAccess or VB.NET

[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.

 

[Brian P. Hammer]

I have actually taken a couple of Access apps and upsized them to .Net. I
have not had any problems with databinding outside of the learning curve.
..Net is much more powerful and robust. If you are going to have multiple
users then .Net is much easier to do record verification. Reporting is also
much more powerful using Crystal or the various third party providers out
there.

 

[Rhett Gong [MS]]

Hi,

Thanks for choosing Microsoft MSDN newsgroup!

We would appreciate your patience while we are looking into this issue. We
will update you as soon as we have update for you! Thanks again!

Rhett Gong[MS]
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no rights.
Please reply to newsgroups only. Thanks.

 

[a]

I would be glad to post this in the Newsgroup if you prefer. I have a few
brief questions that may help me here.

In Access, I have made substantial use of Subforms in ContinuousForm view,
which have ComboBoxes on them. How do you get around this using DataBinding
in VB.NET? Is there databinding that can handle the relationships here, or
do you redesign the GUI based on the 'limitations' of VB.NET?

Do you use a custom DataGrid with Combobox Columns?

Do you use "AutoIncrement" columns in SQL Server, or write your own ID's?

Do you use DataSets, or custom business objects?



Thanks for taking a few minutes to help out. I am pretty good with VB.NET (I
have spent 3 years with it), and I would like to take this project on in VB.



Thanks!

 

[Brian P. Hammer]

The continuous forms is a feature I like in Access but do not think you can
reproduce in .Net. To get around this (in my case it worked) I added a
combo box to my form and based its data off the same dataset and the record
as my dataform. As a user changes the combo, the record changes. The combo
boxes I have set up just like I did in Access. Some are lookups based on a
couple of tables while some are editable and stored in my SQL.


I use the Component One controls, including their data grid. I think they
are more powerful then the .Net ones. You can get them for free at
http://www.componentone.com/microsoft/MicrosoftNK.aspx

The ID number is my own. I use a created ID number based off of company
data. Company Name, Code (always unique) and address. I take all the
letters, convert it to a number and then I have my ID. Each record bases
its record ID off this number.

I use datasets and dataviews and in some cases, some good ole ADO.

HTH,
Brian

 

[a]

Thanks! There are SOOOO many ways to skin a cat in .NET, its nice to have
some guidance.

Kevin

 

[Tom Unkefer]

I have managed to create a reasonable facsimile of an
Access continuous sub-form in VB.net, though so far this
is only in a demo, not a live application.

In general terms:
-I have a frmMain that is an MdiParent and has a scrolling
panel control. frmMain has a DataSet containing the rows
to appear in the "sub-form"
-I instantiate as many frmDetail MDI children as needed
for the DataSet contents, add them to the panel control
and position them. I keep a reference to each child in an
array.
-Each frmDetail has a tgtRow property of type DataRow that
is et to the appropriate rowin the DataSet. The tgtRow
property's Set method loads the data into the various text
and other controls in frmDetail. The property's Get
method moves data from the controls back into the dataRow
and returns it.
-frmMain determines when to do Gets on each MDI child to
get updated dataRows, move them into the DataSet and
update it.

More work than I would like but it isn't too bad once you
have the technique worked out.
======================================================

 

[Ying-Shen Yu[MSFT]]

Hi,

I'm reviewing this issue, our community members has given several ideas on
this topic.
Does it helpful to solve your problem?
If you have still have questions on this issue, please be free to reply
this thread.

Thanks!

Best regards,

Ying-Shen Yu [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, "online" should be removed before
sending.

 

[Guest]

Hi Tom,

I would like to take your "facsimile" of an Access continuous sub form, if it's possible ? I really need this to display the large records that don't fit a single line dimention. You've discribed it pretty well, but I would like to see what it looks like.
Thanks very much in advance

Anna