DataBase - MDB (Access 2002-2003) file format in Access 2007

Asked By samah
09-Apr-08 10:29 AM
Access Learner. Access 2007.

If I create a database in Access 2002-2003 file format in Access 2007
and then split the mdb file into BE and FE, can I use copies of the same
FE in both Access 2007 and Access 2003? Or I have to modify it to use it
in Access 2003?

Thank you in advance.

-samah
SQL Server
(1)
Access 2003
(1)
Access 2007
(1)
Office
(1)
Database
(1)
TWickerath
(1)
RBrandt
(1)
Wickerath
(1)
  Pete D. replied...
09-Apr-08 10:35 AM
Yes you can
  aaron.kemp replied...
09-Apr-08 09:27 PM
well this _DIRECTLY_ contradicts what someone said on the newsgroup
yesterday.

Access 2007 front end and back end
or
Access 2003 front end and back end
or
SQL Server and don't toy with this linked table _CON_.

Sorry

-Aaron



d
in
  aaron_kemp replied...
09-Apr-08 09:27 PM
This answer is not consistent with another answer on the newsgroup the
other day.

Access 2003 w/ Access 2003.
or
Access 2007 w/ Access 2007.
or
Access _ANYTHING_ with ADP.

You be the judge/


d
in
  AOS168b AT comcast DOT net replied...
09-Apr-08 12:52 PM
I recommend that you do your development work using the lowest common
denominator, ie. your copy of Access 2003. For one thing, if you are used to
using the wizards, you'll find that in Access 2007, the wizards tend to
create what is called "Embedded Macros". These are not supported in Access
2003, so, for example, you can quickly discover that you have command buttons
that do nothing when you develop in Access 2007 and then later open with
Access 2003.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
  Pete D. replied...
09-Apr-08 12:52 PM
Access 2007 can use the 2000-2003 version.  2003 cannot use the 2007 version
as it has new features/file formats, which I believe was your question.
  samah replied...
09-Apr-08 03:10 PM
Thank you for your guidance, Tom. While using wizards in Access 2007, is
there any way to avoid Embedded Macros?

Thanks again.
-samah
  BruceM replied...
09-Apr-08 03:25 PM
No contradiction.  If the file format is Access 2003, as stated by the OP,
it can be used with both Access 2003 and Access 2007.  It doesn't matter in
which version of Access it was created.  If a file is created in Access 2007
format it can be used only with Access 2007.  As I understand the FE and BE
need to be the same file format.

well this _DIRECTLY_ contradicts what someone said on the newsgroup
yesterday.

Access 2007 front end and back end
or
Access 2003 front end and back end
or
SQL Server and don't toy with this linked table _CON_.

Sorry

-Aaron
  Rick Brandt replied...
09-Apr-08 07:35 PM
The back end can be the same version or any older version.  An older version
back end is common where multiple users don't all have the same Access
version installed.  In that case the back end is in the oldest version of
all those used as front ends.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt   at   Hunter   dot   com
  George replied...
09-Apr-08 07:53 PM
Here's a relatively common sense way to think about this whole issue without
wading into the arcanity, or dogma, of versioning.

Access 2003 is an earlier version than Access 2007. As with other kinds of
software, newer versions of  Access (e.g., 2007) can usually handle files
created in prior versions (e.g., 2003). Therefore, it makes sense that
Access 2007 can open either an accdb (the newer format) or an mdb (the older
format). So far as I have read anywhere in MS published statements, there is
nothing to contradict that/

Again. as a general rule, it is also true that older versions of software
can not handle newer versions. It should be pretty obvious why. The older
version has no way of "knowing" about the features of the newer version, so
it couldn't possibly be expected to handle it.

Therefore, it makes sense that Access 2003 can not open an mdb, but not an
accdb; Access 2003 has no way of knowing what the accdb format is.

The crux of the issue, of course, is that Access 2007 can create files in
either format, mdb or accdb. Being an mdb, in the format Access 2003 already
knows about, Access 2003 can indeed open the mdb just as well as it could
any mdb created in Access 2003.

If you look at other applications in the Office Suite, I believe, you'll
find "Save As" options for both newer (.docx, .xlsx) formats and older
formats (.doc, .xls). Nothing really unusual at all there.

Of course, if gets more complicated than that, as there are also mdbs
created in earlier versions of Access (97, 2000 and 2002). It's probably not
worthwhile wading through all of the compatibilities/incompatibilities in
all the versions out there. We're really only concerned about the two newer
versions anyway.

The point here is that an mdb which conforms to the Access 2003 format can
be opened, or linked to, from either 2003 or 2007. The reverse, of course,
is not true. An Access 2003 mdb could not be expected to link to an Access
2007 accdb as the back end because it wouldn't have any way of knowing how
to do that.

I second Tom's recommendation to go with the "lowest common denominator", at
least partially for the reasons stated above.

Plus embedded macros, while an improvement over the macros of an earlier
day, are, alas, still macros. And, they are one of those "newer version"
features that make don't work in an older version.

George
  Pete D. replied...
09-Apr-08 08:22 PM
All good but filesearch killed all previous versions, as always ask the
question and be prepared to tweak it as the problems occur.  Also default
settings of new versions can eat your lunch so upgrade slowly, make one
good, two good and expand slowly.  You address this but I felt repeating was
worth it.
  AOS168b AT comcast DOT net replied...
09-Apr-08 09:08 PM
Hi Samah,

No, I'm sorry to say that there is not. This has been raised as a suggestion
to the Access Development Team at Microsoft, for consideration in Access 14.
Hopefully, they will respect user's desire for choice, instead of forcing
their choice upon users.

May I suggest that you navigate to connect.microsoft.com and fill out an
application to be added to their Access list. That way, you can file this
issue directly. They do listen to customer complaints.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________
  George replied...
15-Apr-08 02:32 AM
Thanks, I am always grateful for the assistance of a good editor.

George
Create New Account
help
Might be outgrowing Access but daunted by SQL Server DataBase I am close to completing the consolidation of various small Access databases and a couple of Excel spreadsheets that my little company uses (5 staff) into an all encompasing Access database and I was planning on splitting the database when I was finished to allow simaltaneous use of it by staff on our small
Access 2010 with Sharepoint 2010 DataBase I found this article http: / / sharepointproconnections.com / Articles / tabid / 149 / nodeid / 1996 / SharePoint-Wish-List to me was these two points: client." Hopefully this means you can test out the Access 2010 in a browser capabilities. 2.0 AA compliance. Level 1 browsers, which support 100 on other platforms. Level 2 browsers will have some limitations in rendering and behavior." Bob Access Discussions SQL Server (1) MySQL (1) Visual Basic for Applications (1) SharePoint (1) Access 2007 (1) Access 2010 (1) Office 2003 (1) Windows 7 (1) Well, the question is do
SQL query slow DataBase Hi In the code below I found that it takes 1.3 seconds to load. There is a possible reason, it reads from a local MDB file (access), and it reads from some 270000 rows (result some 15-20 rows, where the highest are counted 150000, 50000, 40000, 26000, remaining are 100's). This is probably more Access that Visual Studio, though - is there a way to split it up or cancel the query? And can I read this faster? string sql = EquipmentID(Equipment) + StartDate.ToOADate().ToString(FloatFormat, myCulture) + EndDate.ToOADate().ToString(FloatFormat, myCulture sql + = " group by event_id, name"; _Log("Calc thread #2"); OleDbCommand com = new OleDbCommand(sql, con); _Log("Calc thread #3"); From #2 to #3 it takes 1.3 seconds. Remaing code takes less that 0.1 second. So the query is what slows it down. Access Discussions SQL Server (1) Linson Unlike Albert D. Kallal (1) MySQL (1) Windows Server 2003
Access 2010 for software development DataBase Hi, What do I need to use Access 2010 (or perhaps 2007) to port our 2003 application and create an executable (MDE in Access 2003)? Are there any issues with 2010? -paulw Access Discussions SQL Server (1) SharePoint (1) Albert D. Kallal (1) Office 2007 (1) Office 2003
SQL Server DataBase Hall?schen, ich habe mit einem SQL Server noch nie was am Hut gehabt. Alles was ich bisher gemacht hatte, da war Access immer ausreichend. Nun aber ist eine Anforderung, das ein Backend auf einem SQL-Server laufen soll, wobei dar?ber noch nicht fertig diskutiert ist. Ich habe da noch eine