Access backup

[a a r o n . k e m p f]

Look dude-- I don't need to use a platform that crashes and hangs with
a trivial amount of data.

In Microsoft's own words....
The following comes from Microsoft article Q300216.

-----------------------------------------------------------------------------------------------------------------------------------------------------------
"Microsoft Jet is a file-sharing database system. A file-sharing
database is one in which all the processing of the file
takes place at the client. When a file-sharing database, such as
Microsoft Jet, is used in a multiuser environment,
multiple client processes are using file read, write, and locking
operations on the same shared file across a network. If,
for any reason, a process cannot be completed, the file can be left in
an incomplete or a corrupted state. Two
examples of when a process may not be completed is when a client is
terminated unexpectedly or when a network
connection to a server is dropped.

Microsoft Jet is not intended to be used with high-stress, high-
concurrency, 24x7 server applications, such as Web,
commerce, transactional, and messaging servers. For these type of
applications, the best solution is to switch to a true
client/server-based database system such as Microsoft Data Engine
(MSDE) or Microsoft SQL Server. When you use
Microsoft Jet in high-stress applications such as Microsoft Internet
Information Server (IIS), customers have reported
database corruption, stability issues such as IIS crashing or locking
up, and also a sudden and persistent failure of the
driver to connect to a valid database that requires re-starting the
IIS service."

 

[a a r o n . k e m p f]

I agree that all C&R should be avoided.

Move to SQL Server and seperate your _DATA_ from your _APPLICATION_.

 

[Gina Whipp]

The title to which Aaron refers to is:

How to keep a Jet 4.0 database in top working condition in Access 2000

Link: http://support.microsoft.com/kb/300216

Maybe you could find something more recent and pertinent?
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II


message
Look dude-- I don't need to use a platform that crashes and hangs with
a trivial amount of data.

In Microsoft's own words....
The following comes from Microsoft article Q300216.

-----------------------------------------------------------------------------------------------------------------------------------------------------------
"Microsoft Jet is a file-sharing database system. A file-sharing
database is one in which all the processing of the file
takes place at the client. When a file-sharing database, such as
Microsoft Jet, is used in a multiuser environment,
multiple client processes are using file read, write, and locking
operations on the same shared file across a network. If,
for any reason, a process cannot be completed, the file can be left in
an incomplete or a corrupted state. Two
examples of when a process may not be completed is when a client is
terminated unexpectedly or when a network
connection to a server is dropped.

Microsoft Jet is not intended to be used with high-stress, high-
concurrency, 24x7 server applications, such as Web,
commerce, transactional, and messaging servers. For these type of
applications, the best solution is to switch to a true
client/server-based database system such as Microsoft Data Engine
(MSDE) or Microsoft SQL Server. When you use
Microsoft Jet in high-stress applications such as Microsoft Internet
Information Server (IIS), customers have reported
database corruption, stability issues such as IIS crashing or locking
up, and also a sudden and persistent failure of the
driver to connect to a valid database that requires re-starting the
IIS service."

 

[BruceM]

I didn't say all C&R should be avoided, just that automatic C&R can lead to
problems. I do split the data from the application. When I do additional
work on the FE I do C&R before deploying the new FE.

message
I agree that all C&R should be avoided.

Move to SQL Server and seperate your _DATA_ from your _APPLICATION_.

 

[Arvin Meyer [MVP]]

message

Move to SQL Server and seperate your _DATA_ from your _APPLICATION_.

It doesn't matter which engine you use, data should always be separated from
the application, especially if there is more than one user or the data is on
a server.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

 

[a a r o n . k e m p f]

Arvin;

but-- on the other hand-- THREE TIERS of jet is called unnecessary

 

[a a r o n . k e m p f]

you don't split shit Bruce

you do what they say because you're a ****ing _TOOL_ kid.

With Access Data Projects, multiple people-- or multiple computers
with the same person or multiple applications with one person on one
computer-- can edit a database at the same time.

You never get 'the file is in use'
You never have to 'compact and repair' because SQL Server does it
automagically
You can take good valid backups _WHILE_ people are using the database
You get built in audit trails of all objects changes-- DDL triggers in
SQL 2005 is a shining example of somehting that isn't available in
Jet, but it's free and very nice and very important to implement any
sort of 'change management' strategy.

Using Jet doesn't even allow you to keep track of DDL change scripts.

SQL Server handles most of this for you-- without making you write a
bunch of obsolete DAO to do anything.

SQL Server sprocs can get called from a webpage.
Can your Access queries get called from a webpage?

What about when they have VB functions in them?

What then?

Aren't you just sick and tired of stacking a query on top of another
query and Jet throws a tissy 'the parameter is incorrect'
or whatever the fck error message Jet decides to spew that day.

I grew sick and tired of Jet crappiness a decade ago.
Just like most of the real database people in the real world.

Just because a couple of grayheads thinks that every business system
should be in Linked Tables-- and just because they're bitter dipshits-
that doesn't mean that you need to become one also.

It's time to grow up and shut up and learn SQL.

I'm not always wrong when I reccomend SQL Server.
Anyone using Jet for any reason whatsoever is always wrong because Jet
****ing sucks, it's slow, it's buggy and it requires a bunch of code
to do anything.

What happens when you need to upsize that code to somewhere else ??
VENDOR LOCKIN.

You have it when you use MS Access, you don't have it when you use SQL
Server.