I have no practical application that I need help with but just a few questions on function of VB. I am obviously new to VB programming, but I have used VBA in many ways in my Access databases (although in no way an expert in VBA though).
My first question is, well I figured out how to link to other databases, but can you store your own data tables when creating a vb application? If it is possible, I understand that probably in many cases it would be unpractical to do so and linking would be the way to go, but then that would bring up my next question...
Lets just say I were to recreate one of my Access databases in VB (I plan on doing so BTW, but just for sake of learning), linking to the original Access tables. When I distribute my application, do those computers need Access installed anyway? For example, lets say I create a "tables only" db in access, then transfer that .mdb file to a PC (or server) that DOES NOT have Access installed, I also copy my VB app to workstations WITHOUT Access but linking to that .mdb file. Would that work? Or what would be the correct way accommodate the scenario of not having Access installed?
A different question is when assigning different references when designing your app in VB, when you put your app on a different PC, how does it work if those references ARE NOT available on those PC's. Is there any way to include them when compiling an .EXE
Thanks for answers. There is no need for detailed explanation for these questions yet (unless you want to). When the time comes, I may repost for detailed explanations.
My first question is, well I figured out how to link to other databases, but can you store your own data tables when creating a vb application? If it is possible, I understand that probably in many cases it would be unpractical to do so and linking would be the way to go, but then that would bring up my next question...
Lets just say I were to recreate one of my Access databases in VB (I plan on doing so BTW, but just for sake of learning), linking to the original Access tables. When I distribute my application, do those computers need Access installed anyway? For example, lets say I create a "tables only" db in access, then transfer that .mdb file to a PC (or server) that DOES NOT have Access installed, I also copy my VB app to workstations WITHOUT Access but linking to that .mdb file. Would that work? Or what would be the correct way accommodate the scenario of not having Access installed?
A different question is when assigning different references when designing your app in VB, when you put your app on a different PC, how does it work if those references ARE NOT available on those PC's. Is there any way to include them when compiling an .EXE
Thanks for answers. There is no need for detailed explanation for these questions yet (unless you want to). When the time comes, I may repost for detailed explanations.