windows xp, access 2003, compact/repair, can't open another mdb till done

[Roger]

if I make a copy of northwind.mdb sample and import data till it
reaches 350Gb in size
and then I make a second copy of northwind

then I open nw1.mdb and do a compact / repair that takes 30-60 seconds
opening the nw2.mdb won't happen until compact repair is done
ditto if importing lots of data in nw1
ditto if inserting sql server data in a table within nw1

what's the solution ?

['69 Camaro]

Hi, Roger.

if I make a copy of northwind.mdb sample and import data till it
reaches 350Gb in size

Wow! Are the fish you catch 50 footers, too? ;-)

what's the solution ?

Perhaps a workstation capable of multi-threading?

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.

[Roger]

On Jun 12, 5:46 pm, "'69 Camaro" <ForwardZERO_SP AM.To.
69Cam...@Spamea ter.orgZERO_SPA Mwrote:

Hi, Roger.

if I make a copy of northwind.mdb sample and import data till it
reaches 350Gb in size

Wow! Are the fish you catch 50 footers, too? ;-)

what's the solution ?

Perhaps a workstation capable of multi-threading?

HTH.
Gunny

Seehttp://www.QBuilt.comf or all your database needs.
Seehttp://www.Access.QBui lt.comfor Microsoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com...utors2.htmlfor contact
info.

typo... 350Mb...

[Roger]

On Jun 12, 5:02 pm, Roger <lesperan...@na tpro.comwrote:

if I make a copy of northwind.mdb sample and import data till it
reaches 350Gb in size
and then I make a second copy of northwind

then I open nw1.mdb and do a compact / repair that takes 30-60 seconds
opening the nw2.mdb won't happen until compact repair is done

ditto if importing lots of data in nw1
ditto if inserting sql server data in a table within nw1

what's the solution ?

creating an access2003 MDE (nw2.mde) solves the problem, where it now
opens immediately even if nw1.mdb is doing a compact / repair
another difference between access97 & access2003, if you open NW2.mdb
twice in access97 you get 2 distinct processes running. With
access2003, you get only one process, unless you create an MDE, then
you get two (or more processes) running

['69 Camaro]

Hi, Roger.

With
access2003, you get only one process, unless you create an MDE, then
you get two (or more processes) running

If you're willing to accept the defaults, then yes, that's what you get.
Double-clicking on the name of the database file in Windows Explorer tells
the operating system, "I'm in too big of a hurry or I'm too lazy to give any
instructions, so just open this file with whatever command line assignments
someone else set up for me on this computer," unless of course you,
yourself, set up the command line parameters for the default file action.

To change this default behavior, you can change the default action for any
specific registered file types (and please note that I'm _not_ recommending
this, only pointing it out as one method to avoid the behavior you're
witnessing), or use a Windows shortcut that specifically names the complete
paths to the executable file and the file to be opened (with or without
assigning command line parameters). Double-click on the same Windows
shortcut twice, and you'll launch two separate processes that open the same
database file.

The reason the behaviors are different in Access 97 and Access 2003 is
because Microsoft wasn't as "helpful" in automating processes for the user
back when Access 97 was designed.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.

[Roger]

On Jun 14, 10:41 am, "'69 Camaro" <ForwardZERO_SP AM.To.
69Cam...@Spamea ter.orgZERO_SPA Mwrote:

Hi, Roger.

With
access2003, you get only one process, unless you create an MDE, then
you get two (or more processes) running

If you're willing to accept the defaults, then yes, that's what you get.
Double-clicking on the name of the database file in Windows Explorer tells
the operating system, "I'm in too big of a hurry or I'm too lazy to give any
instructions, so just open this file with whatever command line assignments
someone else set up for me on this computer," unless of course you,
yourself, set up the command line parameters for the default file action.

To change this default behavior, you can change the default action for any
specific registered file types (and please note that I'm _not_ recommending
this, only pointing it out as one method to avoid the behavior you're
witnessing), or use a Windows shortcut that specifically names the complete
paths to the executable file and the file to be opened (with or without
assigning command line parameters). Double-click on the same Windows
shortcut twice, and you'll launch two separate processes that open the same
database file.

The reason the behaviors are different in Access 97 and Access 2003 is
because Microsoft wasn't as "helpful" in automating processes for the user
back when Access 97 was designed.

HTH.
Gunny

Seehttp://www.QBuilt.comf or all your database needs.
Seehttp://www.Access.QBui lt.comfor Microsoft Access tips and tutorials.
Blogs:http://www.DataDevilDog.BlogSpot.com...utors2.htmlfor contact
info.

cool.. that did the trick.. thanx

['69 Camaro]

cool.. that did the trick.. thanx

You're welcome. Glad to help.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.