Visual Basic Front End and Access as Back End

[randolphoralph]

I have created a MS Access Database and then found out that the users that need to enter and edit information in the database do not have MS Access installed on their computers due to licensing issues. I was going to use the Access runtime and change the database from MDB to MDE but I found out that due to Security Issues the Administrator will not allow anything to be installed including the Access runtime.

I have never run across this issue and not sure where to begin to work around this issue.

I was thinking about using Visual Basic as a Front End for the users to enter data and Access as the Back End to run reports and queries.

Can anyone provide some help on how to do this as I have never had to use VB and Access together?

Or if someone knows of a better way I would really appreciate any help.

 

[Atomic Shrimp]

You'll want to check that the administrator will allow the installation of the VB runtime DLLs (they're included on most Windows machines by default, I think, but if yours are a custom build, there's no telling).

VB front end for an Access DB is certainly quite do-able, but there are lots of things you might be comfortable doing in the VBA behind Access forms that just won't be possible any more (well, not nearly so easily, I mean) - because VBA in Access is very tightly integrated with the database itself.

It will probably be quite hard work. My inclination would be try to get the Administrator to adapt his policy - if necessary, by telling the users that they just can't have it - let them do the ear-bending. (I appreciate this maybe isn't a particularly useful suggestion for all contexts, but if you're not allowed the tools you need to do the job...)

 

[randolphoralph]

Where would VB runtime DLLs be stored on the computer?

I can check and see if they are installed since it is a custom build. I do know that the some users have MS Office XP Professional which includes Access but then their are some users that have MS Office Standard installed with no Access. I am not sure if it includes the Access runtime or not.

I agree that it would be easier to use MDE and use the runtime then have to do VB as front end.

Thanks you for the help!

 

[HiTechCoach]

If there can install Office, then why not the Access runtime. That doesn't make a lot of sense because the Access full and runtime versions are basically the same files except the design feature are disabled.

If you will not be able to install the Access Runtime for security reasons, then you probably will not be able to install a VB app. I would definitely check with them before you make a decision.

If there is a web server available, you could use ASP pages or DAPs in a web browser for data entry.

 

[Atomic Shrimp]

If you will not be able to install the Access Runtime for security reasons, then you probably will not be able to install a VB app. I would definitely check with them before you make a decision.

That's a good point that I overlooked - a VB-produced executable written by a single individual is arguably a less safe thing to install (from the POV of a sys admin) than the Access runtime, which has a whole team of testers and developers behind it.

 

[Banana]

Not to mention that one poster here once pointed out that it's actually easier to decompile a VB exe than a MDE (provided that you've used EverythingAccess.com's product to strip away the compiler junk)

 

[randolphoralph]

Sounds to me like I need to talk with the Admin before going any further.

Thanks to everyone for the great responses.