469,337 Members | 5,972 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,337 developers. It's quick & easy.

.mdb or .accdb?

ARC
I have another question. With Access 2007, as I understand it, you only need
to use the .accdb if you are using features such as memo notes history, or
the multiple selections for a given key id.

Prior to deploying my program in Access 2007, I need to make sure I'm using
the correct formats. I have a handful of misc. databases, one for workspaces
/ temp. tables, local config options and a to-do list. Should I use the .mdb
format for these, instead of the .accdb? I guess I'm wondering about speed,
and if the .mdb is faster / more stable, maybe I shouldn't be using the
..accdb at all?

Anyone have any experience with the pro's and cons for .mdb versus .accdb?

Many Thanks,

Andy
Aug 20 '07 #1
4 7205
>
Anyone have any experience with the pro's and cons for .mdb versus .accdb?

Many Thanks,

Andy
I think the deciding factor would be what version of ms-access the end users
have.

If you using the new free "runtime", or expect all users to have a2007, then
use the new format.

If you going to have different versions (say, a97, a2000, a2003 and a2007)
all working on the same data at the same time (this works), then you have to
use a mdb in the *lowest* common format for the back end file.

So, sure...use the new format.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
Aug 20 '07 #2
ARC
Oh yes, a couple more questions. So if I add RE, should I then go through
all my code and remove instances where I do the RE myself? Also, when I
write ugprade code to import user's existing data from A97, what will happen
on the import if there is orphaned data? I would assume it would simply not
import, which would be desired actually.

Thanks again, Albert.

Andy
"Albert D. Kallal" <Pl*******************@msn.comwrote in message
news:VXoyi.74978$rX4.46052@pd7urf2no...

Anyone have any experience with the pro's and cons for .mdb versus
.accdb?

Many Thanks,

Andy

I think the deciding factor would be what version of ms-access the end
users have.

If you using the new free "runtime", or expect all users to have a2007,
then use the new format.

If you going to have different versions (say, a97, a2000, a2003 and a2007)
all working on the same data at the same time (this works), then you have
to use a mdb in the *lowest* common format for the back end file.

So, sure...use the new format.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

Aug 21 '07 #3
ARC
I'll be distributing the runtime. However, end user's could potentially have
functions to link to the data for other reasons.

The only new things I've tried to use are the RTF on memo fields, and I
tried the option for keeping memo history (which I understand necessitates
the .accdb file). However, I can't get the memo history to work, even with
the new table setting set to yes. So maybe I should resave all db's as
straight .mdb's.
"Albert D. Kallal" <Pl*******************@msn.comwrote in message
news:VXoyi.74978$rX4.46052@pd7urf2no...

Anyone have any experience with the pro's and cons for .mdb versus
.accdb?

Many Thanks,

Andy

I think the deciding factor would be what version of ms-access the end
users have.

If you using the new free "runtime", or expect all users to have a2007,
then use the new format.

If you going to have different versions (say, a97, a2000, a2003 and a2007)
all working on the same data at the same time (this works), then you have
to use a mdb in the *lowest* common format for the back end file.

So, sure...use the new format.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

Aug 21 '07 #4

"ARC" <an**@andyc.comwrote in message
news:0Z*****************@newssvr19.news.prodigy.ne t...
Oh yes, a couple more questions. So if I add RE, should I then go through
all my code and remove instances where I do the RE myself?
Well, the deleting part, sure..you might want to remove that code. As I
noted in the other post, I consider still a good idea to "test" for child
records when you do NOT want a deletion to occur in those cases.
Also, when I write ugprade code to import user's existing data from A97,
what will happen on the import if there is orphaned data? I would assume
it would simply not import, which would be desired actually.
Yes, if you enforce relationships, then importing orphaned data into a child
table is not permitted, and they will be ignored...
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
Aug 21 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

34 posts views Thread by radink | last post: by
4 posts views Thread by MrDeej | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by suresh191 | last post: by
1 post views Thread by Marylou17 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.