- #Visual basic aplicaciones access how to
- #Visual basic aplicaciones access install
- #Visual basic aplicaciones access software
- #Visual basic aplicaciones access code
However, even if you do embed this application inside of your. net application as opposed to just launching it. I suppose you might get some kind of "gee wiz" factor from having the form and application appear inside of the. You can certainly use VSTO and inter-op to embed this application, but you simply under the covers are still going to be launching Access, and you STILL require your Access application. Why not just have a simple button that launches Access from your. However, I am not really sure it makes a lot of sense to embed your existing application. So, the answer is yes, you can embed this application and use inter-op from Visual Studio. net anyway? If Access works, then why not continue to use Access?) (in fact, this quite much begs why one is attempting to use. In other words, you are not reducing the number of systems and thus you not reducing the cost of running such systems, but in fact increasing costs here. All you doing is tossing another layer of complexity here and another layer of having to use dollars to support your application and ALSO that of theĪccess application. I would suggest you build the email gathering using the features of. net and "embed this" means you not really gaining a whole lot here, have you? In other words, attempting to do this from. And so now you succeed in embedding this, but you still have all of the support and issues that go along with that Access application. Not only are you going to require having Access installed, but also your application. Is already working and built and paid for. net application, but at the end of the day is really is a bunch of makeup and lipstick on something trying to look cool all the while using up valuable resource dollars to do something that In other words, it might sound all very "cool" that you have this. I really makes about zero sense THEN to embed that part into.
#Visual basic aplicaciones access install
If you going to use Access then you will have to install + maintain + update + write that Access code. If you going to embed, then you need Access. You probably can embed your application if you use automation. If you going to consider and continue to use Access, then my following article on using the Access runtime and deployment system here should help you explain some options you have for distribution of your applciation when using Access. This is YOUR choice to make here, not ours. As noted when you use these tools, then you'll not be using the features of access anymore and don't require AccessĪt all and thus this comes down to what "shop" you going to hang around for advice. If you decide to not use Access, then you have to dump the use of access, and adopt a different set a programming tools such as c# or vb.net. You can then take that runtime system and have it packaged up using a commercial quality installing system such as what is offered by sagekey. You can stick to using access and obtain a commercial quality installing ability by utilizing the access runtime. The same goes for whichever the TWO choices above have been outlined to you. I'm not sure that it needs explaining here that a tea shop is not the correct choice here and you need find a coffee shop if you looking for coffee.
#Visual basic aplicaciones access how to
Your situation is really no different than you walking into a tea shop, and hoping you will find a bunch of people that will that will give you advice on how to purchase coffee, how to grind coffee, how to roast coffee beans or even just obtain some equipment
#Visual basic aplicaciones access software
I mean realistically at this point, we're not really talking about software anymore, but a general approach to how you solve and pursue a particular goal in life here. This choice means you NOT going to use Access anymore for your solution. net groups and forums since this Access group will be of little use. net here (c# or vb) then you need to spend some time on some. So if you going to make the choice to use. You simply not are going to get any much advice or good links to resources in learning VB.net in this form anymore than of using Oracle or FoxPro to develop your solution. On the other hand bingGoogle is your friend.
#Visual basic aplicaciones access code
net and writing code in those systems, then this is the WRONG forum. If you looking for suggestions and resources on learning. This would allow you to continue to use Access and thus not need to adopt some other programming and development system such as c# or vb.net.ĭon't develop the application in Access. You have two basic roads and choices here:ĭevelop the application in Access and use a commercial installing system such as what the folks at I not sure what more suggestions you are looking for.