VB application not requiring Access

stoyleg

New member
Local time
Today, 11:17
Joined
Jan 18, 2012
Messages
7
I want to recreate an Access database I've made as a standalone application for users who potentially do not have Access.

Is it possible to generate an .exe file which includes an Access or SQL Server 'backend' but doesn't require either databases to be bought by the end user?
 
If you want to build a freely distributable VB app packaging it as a .EXE file, then you are describing the real VB product and not Access which offers VBA.
 
If you want to use Access as a front end:
http://support.microsoft.com/kb/842004 (for 2003)
http://technet.microsoft.com/en-us/library/cc751805(office.12).aspx (2007)

it is also possible to do something similar in .net as a front end accessing an Access Database backend (or SQL Server) without the user needing Access installed.
From a .net perspective you cannot use any inbuilt Access functions, even if they're in the queries in your backend database. ie you can develop the front end app in .net, create your database using Access and distribute the .exe and the backend .mdb/.accdb file to a user without them needing to have access installed.
 
users can install a free run-time version of Access, which should work, although you need to ensure everything is 100% debugged. You can add this to an installation package yourself.
 
users can install a free run-time version of Access, which should work, although you need to ensure everything is 100% debugged. You can add this to an installation package yourself.
... and ensure you have proper Error Handling in place unless your app will terminate everytime an unhandled error is encountered.
 
Thanks to everyone for their replies :)

I didn't explain myself very well so apologies for that, but tehNellie answered my question.
 
... and ensure you have proper Error Handling in place unless your app will terminate everytime an unhandled error is encountered.
Only if it is an mdb or accdb file. If it is an mde or accde file that statement is incorrect. (I know it sounds suspicious but it is true and Access MVP Albert D. Kallal proved it to me and I've tested it :D )
 
Only if it is an mdb or accdb file. If it is an mde or accde file that statement is incorrect. (I know it sounds suspicious but it is true and Access MVP Albert D. Kallal proved it to me and I've tested it :D )
So what happens if it's an mde or accde? ;)
 

Users who are viewing this thread

Back
Top Bottom