Free for All: help me speed up my Access Database

What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?

hi Anthony,

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?
That's outdated: Access can go Warp 4.5.


mfG
-- stefan --

That's outdated: Access can go Warp 4.5.

Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.

HTH.
Gunny

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


"Stefan Hoffmann" wrote in message
...
hi Anthony,

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?
That's outdated: Access can go Warp 4.5.


mfG
-- stefan --

hi Gunny,

'69 Camaro wrote:
That's outdated: Access can go Warp 4.5.
Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.
Oh, come on, only near the sun, eh?


mfG
-- stefan --

That's outdated: Access can go Warp 4.5.
Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.
Oh, come on, only near the sun, eh?

Right. Without the gravity assist, it can only do Warp 7.

HTH.
Gunny

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


"Stefan Hoffmann" wrote in message
...
hi Gunny,

'69 Camaro wrote:
That's outdated: Access can go Warp 4.5.
Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.
Oh, come on, only near the sun, eh?


mfG
-- stefan --

Actually, if you go to Tools, Options, Interstellar, you can set the default
warp factor.

Also, if you get an error 1701, that indicates a dilithium crystal
contamination. You can put this in your error handler to resolve it:

If err.number = 1701 Then
Application.Crystal.Refresh
End If
--
Dave Hargis, Microsoft Access MVP


"'69 Camaro" wrote:

That's outdated: Access can go Warp 4.5.

Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.

HTH.
Gunny

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


"Stefan Hoffmann" wrote in message
...
hi Anthony,

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?
That's outdated: Access can go Warp 4.5.


mfG
-- stefan --

Hey, stop getting fresh with Crystal! g

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Klatuu" wrote in message
...
Actually, if you go to Tools, Options, Interstellar, you can set the
default
warp factor.

Also, if you get an error 1701, that indicates a dilithium crystal
contamination. You can put this in your error handler to resolve it:

If err.number = 1701 Then
Application.Crystal.Refresh
End If
--
Dave Hargis, Microsoft Access MVP


"'69 Camaro" wrote:

That's outdated: Access can go Warp 4.5.

Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.

HTH.
Gunny

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


"Stefan Hoffmann" wrote in message
...
hi Anthony,

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?
That's outdated: Access can go Warp 4.5.


mfG
-- stefan --

LOL, thanks, but no thanks

I would bet that by now poor Anthony is sorry he ever asked the question.

Trivia question:
Does anyone know why the error code is 1701

--
Dave Hargis, Microsoft Access MVP


"Douglas J. Steele" wrote:

Hey, stop getting fresh with Crystal! g

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Klatuu" wrote in message
...
Actually, if you go to Tools, Options, Interstellar, you can set the
default
warp factor.

Also, if you get an error 1701, that indicates a dilithium crystal
contamination. You can put this in your error handler to resolve it:

If err.number = 1701 Then
Application.Crystal.Refresh
End If
--
Dave Hargis, Microsoft Access MVP


"'69 Camaro" wrote:

That's outdated: Access can go Warp 4.5.

Check your dilithium crystals for surface contaminants. Mine goes Warp 8
when I put the metal to the floor.

HTH.
Gunny

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


"Stefan Hoffmann" wrote in message
...
hi Anthony,

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?
That's outdated: Access can go Warp 4.5.


mfG
-- stefan --

Use a SQL Server backend. And index your tables properly.

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?

Use a SQL Server backend.

No, than does not make my application run faster.

Perhaps you mean 'rebuild your application entirely, using
client-server principles'?

No, that does not make my application run faster.

One of the regular posters here has a relevant comparison:

A sports car is faster than a bus. But a bus can get 30 people
from A to B faster than the sports car.

The bus is SQL Server. It is not faster. Jet is faster.
But SQL Server can do more transactions on a larger
database in the same time.

One of the reasons Jet is faster is that it is a distributed
database engine. Most of the processing takes place on
your workstation. You don't have to share your processor
and memory with all the other people doing transactions.

One of the reasons SQL Server can do more transactions
on a larger database in the same time is that the Jet records
remain locked for longer. Jet does automatic retries when
there is a locking conflict, but it limits the throughput of the
system.

(david)


"ManningFan" wrote in message
ups.com...
Use a SQL Server backend. And index your tables properly.

Anthony wrote:
What does EVERYONE recommend I do to make my database run as close to
lightning speed as possible?