access tables

G

Greg

The data base I'm using is taking a long time to tables and subtables. Does
anyone have any suggestions?
 
S

strive4peace

Hi Greg,

are your tables linked?

if so, it is good to open a table or a recordset to one of the linked
tables while you are working

Warm Regards,
Crystal
*
:) have an awesome day :)
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*
 
T

Todos Menos [MSFT]

I would reccomend not using MDB for anything. It isn't fast enough
for real world use.

Access Data Projects have been the preferred method of Access
development for close to a decade.

Sorry

-Todos
 
S

strive4peace

Greg,

pay no attention to this comment.

(sorry, Aaron, but I do not understand why you use your obvious
intelligence in such non-productive ways)

Warm Regards,
Crystal
*
:) have an awesome day :)
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*
 
D

David W. Fenton

Access Data Projects have been the preferred method of Access
development for close to a decade.

From
http://technet2.microsoft.com/Office/en-us/library/1dce641e-ba1c-446a
-8ff2-221769a58ba51033.mspx?mfr=true :

Access Data Projects (ADPs)

An Access Data Project is an OLE document file, like the .xls
or.doc file formats. It contains forms, reports, macros, VBA
modules, and a connection string. All tables and queries are
stored in SQL Server. The ADP architecture was designed to create
client-server applications. Because of this, there is a limit to
the number of records that Access returns in any recordset. This
limit is configurable, but you typically must build enough
filtering into your application so that you do not reach the
limit.

Access uses OLEDB to communicate with SQL Server. To provide the
Jet-like cursor behavior desired for desktop applications, Access
implements the Client Data Manager (CDM) as an additional layer
between Access and OLEDB.

Because of the layers required to get from Access to SQL Server in
the ADP architecture, it is often easier to optimize MDB/ACCDB
file solutions. However, there are some scenarios where a report
might be generated significantly faster in an ADP file. To add
these performance improvements and retain the flexibility of SQL
Server, you can build the majority of the application in an MDB or
ACCDB file and have the file load reports from a referenced ADP
file.

One advantage that ADP files have over files in MDB or ACCDB
format is the ability to make design changes to SQL Server
objects. ADP files include graphical designers for tables, views,
stored procedures, functions, and database diagrams.

Particularly note the first sentence of the third paragraph:
 
T

Todos Menos [MSFT]

Crystal

I'm sorry that you think that you know what Access is; but you're too
much of a dipshit

go and play with your barbies, bitch
 
T

Todos Menos [MSFT]

MDB = the epitome of non-productive

MDB is a disease anyone that uses it should be fired and then spit
upon
 
T

Todos Menos [MSFT]

Dude
Because of the layers required to get from Access to SQL Server in
the ADP architecture, it is often easier to optimize MDB/ACCDB
file solutions.


GET REAL KID

you are totally full of crap

'because of the layers'
I mean OMFG

there are no layers; SQL SERVER AND VBA.

none of this linked table manager crap
none of this refresh / relink crap

get the sql developers' edition and STFU until you know what the
'Database Tuning Advisor' and 'index tuning wizard' is

David i mean seriously.. have you ever opened 'query analyzer'

have you ever seen PROFILER?

if you had any clue WTF you were talking about you would stop conning
people into MDB


anyone using MDB should be fired and then spit upon
 
T

Todos Menos [MSFT]

However, there are some scenarios where a report
might be generated significantly faster in an ADP file


I mean seriously here David.. have you ever tried to run MDB across a
NETWORK?

MDB doesn't work across ANY network; ADP works across WAN, VPN,
Wireless and the PUBLIC INTERNET

MDB is for babies and retards and lamers
 
Top