I've decided to try and learn VB.net, using VS community 2015. After running through some of the example apps such as Picture Viewer, etc. I decided to take my simplest access application and try and duplicate it in VS.
This app has only 3 tables, minimal VBA code, and keeps track of our engineering changes. It requires no reporting, and only 3 forms. (NavForm, Input form for our tags, Input form for our change records)
Overall, I think VS is neat, but it's amazing how long it's taken to make this simple app so far...and I'm far from done. I'm really questioning if it's worth the extra effort.
One hang up I'm having is that my back end .accdb uses one attachment type field. I've been researching for over a week on how to handle this in VB.net. The only viable solution seems to be DAO, which people are saying shouldn't be used because it's old and outdated. I'm basically at a crossroads, and don't know how to proceed.
Any thoughts appreciated. If anyone has a system for dealing with the attachment type field in VS I'd love to hear it. :banghead:
This app has only 3 tables, minimal VBA code, and keeps track of our engineering changes. It requires no reporting, and only 3 forms. (NavForm, Input form for our tags, Input form for our change records)
Overall, I think VS is neat, but it's amazing how long it's taken to make this simple app so far...and I'm far from done. I'm really questioning if it's worth the extra effort.
One hang up I'm having is that my back end .accdb uses one attachment type field. I've been researching for over a week on how to handle this in VB.net. The only viable solution seems to be DAO, which people are saying shouldn't be used because it's old and outdated. I'm basically at a crossroads, and don't know how to proceed.
Any thoughts appreciated. If anyone has a system for dealing with the attachment type field in VS I'd love to hear it. :banghead: