Re: a question regarding separate mdb's in Access

Tech-Archive recommends: Fix windows errors by optimizing your registry


"JDB" <jdbNewsGroups@xxxxxxxxx> wrote in message
news:cfa3b5da-dd44-4b47-8c09-9382fb93d676@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
1. I am pretty much of an Access hacker ? that is my skill level
2. I had heard I the distant past that an Access program should be
separated into separate mdb?s
So my question
1. Are only the data tables keep in a ?back-end? mdb, and
2. All of the rest put into a front end mdb including Queries,
Reports, Forms and Modules?

Any pointers are welcome.

BTW, I am in the middle of Oceana with no access to any Access books.

Thanks

JDB

-----------------------------------------------------

Yes. You can separate 'code' from the actual data. And you can go about it
in various ways. One is to create a mde file (referred to as a 'Protected
Access Database Application with compiled VBA'). The other is to create an
Access Project (.adp). The former is expected to manage a MDB or Jet
formatted database. The latter to manage an MSDE or SQLServer database.

Another level to consider is that an Access Project or Compiled Application
needs to have the 'runtime' if you want to run it separately, ie, either a
licensed copy of Access is available or a licensed copy of the runtime. You
usually get the runtime through purchasing an "Office Developer's Edition"
at least with MS Access 2000. The developer editions also include additional
tools that make developing applications easier such as VSS, ActiveX
components, viewers and wizards. These tools are not an absolute requirement
they just make development easier.

MS Access when it comes to various 'developer' versions hasn't been quite as
"backward compatible" as we would like. It seems like practically every
version introduced a new tool or terminology.

Now that I have you throughly confused, I suggest that you check out the MS
Access Developer's forums. Clearly state the version of MS Access you are
using (or plan to use) and whether you intend your project to use MDB or
another database.

microsoft.public.access.

hth
-ralph


.

Relevant Pages

  • Re: Migration and authorisations
    ... It's an Access 2000 mdb and we now use Access 2002. ... are in two separate databases you may have two separate sets of security. ... Some networking server software would let you join the two drives into one ... did not mention the database and version or anything like that so you are ...
    (comp.databases.ms-access)
  • Re: access runtime version
    ... that they needed to have access on each of the machines that were going to ... run the database - and this they agreed to. ... leave it as a mdb as there are poeple in the organisation (who do have ... > While the Developer Edition doesn't alter the mdb in any way, ...
    (microsoft.public.access.gettingstarted)
  • Re: Access 2003 security setup
    ... not a specific mdb. ... You really shouldn't keep each groups data in three separate tables. ... I ended up setting the level of security to "very high”. ... The problem now is that when I try to open the database again, ...
    (microsoft.public.access.security)
  • Re: Runtime For Dummies
    ... -A runtime database is essentially a standalone file that contains all ... Also see Microsoft Access Developer Edition FAQ ... You want to split the MDB into a Front End MDB containing the queries, forms, ...
    (comp.databases.ms-access)
  • Re: Distribution of MDE Database
    ... the mdb file?Would that be something like storing a copy ... on a separate drive?Could you detail how would i go about ... making changes once the file is in MDE format? ... >> like to convert my database to MDE to prevent changes to ...
    (microsoft.public.access.security)