Access Front End Applications
-
Hi guys I was just wondering if anyone could tell me what someone means when they say they run an MS access application? Although I'm no stranger to VBA in Excel, and VB6, I am a stranger to MS Access programming. Can MS Access be used as a deployable front end (like a windows form app) for mass use of sorts using VBA? Cheers,
oooo, the Jedi's will feel this one....
-
Hi guys I was just wondering if anyone could tell me what someone means when they say they run an MS access application? Although I'm no stranger to VBA in Excel, and VB6, I am a stranger to MS Access programming. Can MS Access be used as a deployable front end (like a windows form app) for mass use of sorts using VBA? Cheers,
oooo, the Jedi's will feel this one....
Yes, Access can be used to create a front-end, with either the Access/Jet database itself as the back end, or another database. I supported one application that was becoming too big for the Jet database engine, so I upgraded the back-end to SQL Server without too much trouble. It's usually easier to deploy the app if the user already has Access installed, though I believe you can purchase and distribute an Access run-time. The apps I've created or maintained were always for internal users that already had Access installed. Access has its own forms and reports designers and sets of controls, and also supports other COM/OCX controls on the forms, if I recall correctly. With some effort, it's also possible to lock it down so that the source code and form definitions can't be viewed or modified. Scott
-
Hi guys I was just wondering if anyone could tell me what someone means when they say they run an MS access application? Although I'm no stranger to VBA in Excel, and VB6, I am a stranger to MS Access programming. Can MS Access be used as a deployable front end (like a windows form app) for mass use of sorts using VBA? Cheers,
oooo, the Jedi's will feel this one....
I have not actually used Access for a number of years but certainly, we would create a front end containing forms and reports and a separate mdb containing all of the tables or links to SQL server (ahem; it was along time ago). You could then place the front end on a client machine with the back end on a server and connect the users. Not ideal but it worked reasonably well. It was a simple and quick way of getting an application out to a small set of users but I wouldn't do that now. Either a web or winforms front end looking at a sql server database (or whatever your preferred technologies are).
Tychotics: take us back to the moon "Life, for ever dying to be born afresh, for ever young and eager, will presently stand upon this earth as upon a footstool, and stretch out its realm amidst the stars." H. G. Wells
-
Yes, Access can be used to create a front-end, with either the Access/Jet database itself as the back end, or another database. I supported one application that was becoming too big for the Jet database engine, so I upgraded the back-end to SQL Server without too much trouble. It's usually easier to deploy the app if the user already has Access installed, though I believe you can purchase and distribute an Access run-time. The apps I've created or maintained were always for internal users that already had Access installed. Access has its own forms and reports designers and sets of controls, and also supports other COM/OCX controls on the forms, if I recall correctly. With some effort, it's also possible to lock it down so that the source code and form definitions can't be viewed or modified. Scott
Cool, thanks for this. I'll swat up on it tonight. The reason I'm asking is I have been invited for a second interview at a place that currently has and needs to support this set up until a replacement can be sorted (which will be one of my main tasks if I get the job). They currently have about 150 users on this. They have already upgraded the data storage to SQL, but are not quite ready with an updated front end. Wish me luck...
oooo, the Jedi's will feel this one....
-
I have not actually used Access for a number of years but certainly, we would create a front end containing forms and reports and a separate mdb containing all of the tables or links to SQL server (ahem; it was along time ago). You could then place the front end on a client machine with the back end on a server and connect the users. Not ideal but it worked reasonably well. It was a simple and quick way of getting an application out to a small set of users but I wouldn't do that now. Either a web or winforms front end looking at a sql server database (or whatever your preferred technologies are).
Tychotics: take us back to the moon "Life, for ever dying to be born afresh, for ever young and eager, will presently stand upon this earth as upon a footstool, and stretch out its realm amidst the stars." H. G. Wells
Thanks for that. It's for a company that has this in place already, but will be building a new, improved system. Unfortunatly, this system will need maintaining until the new is ready. It's for a second interview I have, so the new system and the maintainence of the old system would be my responsibility if I get it. :)
oooo, the Jedi's will feel this one....
-
Thanks for that. It's for a company that has this in place already, but will be building a new, improved system. Unfortunatly, this system will need maintaining until the new is ready. It's for a second interview I have, so the new system and the maintainence of the old system would be my responsibility if I get it. :)
oooo, the Jedi's will feel this one....
Good luck.
Tychotics: take us back to the moon "Life, for ever dying to be born afresh, for ever young and eager, will presently stand upon this earth as upon a footstool, and stretch out its realm amidst the stars." H. G. Wells