A2010 client
- Thread starter RustyRick
- Start date
- Local time
- Today, 14:34
- Joined
- Aug 30, 2003
- Messages
- 36,256
Lightwave
Ad astra
- Local time
- Today, 22:34
- Joined
- Sep 27, 2004
- Messages
- 1,536
Rusty
There is only one version of the underlying program behind Access 2010
There are however 2 flavours.
Run time as PBaldy indicates and the Full Access Version.
Run time prevents users creating or editing the underlying forms and code although data can be entered depending on the application.
Now the full version can be configured in a number of different ways
1) Where it holds the information along with the front end forms and coding
2) Where it holds the information separate from the front end forms and coding.
In case 2)
The Front end is called the client
and the database (usually held on a server) is called the backend.
There will normally only be one backend but multiple copies of the front end all attached to the back end.
This model is commonly referred to as a two tier system and is a pattern repeated in nearly all database programs.
There is a tool within Access to "Split" databases this simply creates two files were previously there was one. One copy containes the forms and any VBA code (the front end or client) and the other just the tables (back end).
The above holds true for A97/A2003/A2007/A2010/A2013 and will probably hold true for the next version of Access.
There is only one version of the underlying program behind Access 2010
There are however 2 flavours.
Run time as PBaldy indicates and the Full Access Version.
Run time prevents users creating or editing the underlying forms and code although data can be entered depending on the application.
Now the full version can be configured in a number of different ways
1) Where it holds the information along with the front end forms and coding
2) Where it holds the information separate from the front end forms and coding.
In case 2)
The Front end is called the client
and the database (usually held on a server) is called the backend.
There will normally only be one backend but multiple copies of the front end all attached to the back end.
This model is commonly referred to as a two tier system and is a pattern repeated in nearly all database programs.
There is a tool within Access to "Split" databases this simply creates two files were previously there was one. One copy containes the forms and any VBA code (the front end or client) and the other just the tables (back end).
The above holds true for A97/A2003/A2007/A2010/A2013 and will probably hold true for the next version of Access.
I can "Save and Publish" an ACCDE file. So that must be the full blown version eh?
Isn't that all I need to develop something I can place locked down version in some of our off site offices?
Thanks for your detailed response.
Isn't that all I need to develop something I can place locked down version in some of our off site offices?
Thanks for your detailed response.
Lightwave
Ad astra
- Local time
- Today, 22:34
- Joined
- Sep 27, 2004
- Messages
- 1,536
an ACCDE is actually a runtime version.
Yes you will need a version of Access on the target machines. You may wish to think about getting your data synchronised. Access doesn't work well of wide area networks. This may be a problem for you.
Think of the run time version like a pdf compared with the full version which is more like a word document.
Just like pdf's you do need adobe on the machine to view them.
So to use an accde version you will need at least a run time version on the target computer.
In the case of Access 2010 - you can get a free run time version of access which will allow the running of published databases.
Yes you will need a version of Access on the target machines. You may wish to think about getting your data synchronised. Access doesn't work well of wide area networks. This may be a problem for you.
Think of the run time version like a pdf compared with the full version which is more like a word document.
Just like pdf's you do need adobe on the machine to view them.
So to use an accde version you will need at least a run time version on the target computer.
In the case of Access 2010 - you can get a free run time version of access which will allow the running of published databases.
Last edited:
Another aspect to A2010 and later applications, which hasn't been mentioned here so far, but may be contributing to your confusion, is the web database. A web database is what you would "Publish", but in this context "Publish" means to upload your application to a Sharepoint site with Access Services, and you would then be able to share the application oven a wide network and users could run your web forms in a browser (that's the basic idea anyway). Web databases can have both web objects (queries, forms and reports) and client objects. Web objects can run in a browser or in the client (in this case the term client means within Access itself). Client objects, as the name implies, can only run in the client. Also, web objects have design restrictions that client objects do not (i.e. no VBA, different methods for referencing other objects, layout limitations, etc.).
