P
PhotoGirl1206
Why is it important to capture, record, and save information when using
Microsoft Access 2007?
Microsoft Access 2007?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
B
boblarson
I don't think your question is phrased to well. Why is it important to do
what you asked? Because that's what the program is for. It's a bit like
asking why you put gasoline and oil into a car.
--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
__________________________________
what you asked? Because that's what the program is for. It's a bit like
asking why you put gasoline and oil into a car.
--
Bob Larson
Access World Forums Super Moderator
Utter Access VIP
Tutorials at http://www.btabdevelopment.com
__________________________________
C
Cheyanne
hi
P
PhotoGirl1206
This question was asked by my computer teacher. Either she phrased it wrong
or there is more behind her question. I know it is important to save your
information constantly while working with Access 2007. Why? Why is it
important to capture the information? Why is it important to record the
information? I have only had experience with this database for a few days.
If you could help me with these questions I would really appreciate it. Thank
you.
or there is more behind her question. I know it is important to save your
information constantly while working with Access 2007. Why? Why is it
important to capture the information? Why is it important to record the
information? I have only had experience with this database for a few days.
If you could help me with these questions I would really appreciate it. Thank
you.
M
Matt
The answer that jumps out at me is because any program has the potential to
crash, especially if your jacking with code, and if you don't SAVE OFTEN (as
soon as you've done enough that you wouldn't want to redo it) you leave
yourself open to the great disappointment of losing your work. Save often is
the first rule for all my employees. So if she's referring to having your
work saved by what she said, that's the reason I would vote on.
crash, especially if your jacking with code, and if you don't SAVE OFTEN (as
soon as you've done enough that you wouldn't want to redo it) you leave
yourself open to the great disappointment of losing your work. Save often is
the first rule for all my employees. So if she's referring to having your
work saved by what she said, that's the reason I would vote on.
A
aaron.kempf
I agree. When you're using Access, save before you change views.. save
when you change a couple of things.
Save your changes every few minutes.
Because using a piece of crap database like Access / ACCDB - you're
just effectively playing Russian Roulette with your data.
Move to SQL Server (ADP); your db won't crash- and you won't lose dev
time.
-Aaron
when you change a couple of things.
Save your changes every few minutes.
Because using a piece of crap database like Access / ACCDB - you're
just effectively playing Russian Roulette with your data.
Move to SQL Server (ADP); your db won't crash- and you won't lose dev
time.
-Aaron
T
Tony Toews [MVP]
Matt said:The answer that jumps out at me is because any program has the potential to
crash, especially if your jacking with code, and if you don't SAVE OFTEN (as
soon as you've done enough that you wouldn't want to redo it) you leave
yourself open to the great disappointment of losing your work. Save often is
the first rule for all my employees. So if she's referring to having your
work saved by what she said, that's the reason I would vote on.
There was an amusing story of a VP working on a DOS based spreadsheet
many years ago. Just after the explosion down the street which took
out the power the VP was heard to scream in anguish. Four hours work
- no saving.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
A
aaron.kempf
You can _EASILY_ get corruption with a power outage using MS Access.
Can't you?
Because Access doesn't _REALLY_ support transactions-- things get
halfway committed.
-Aaron
Can't you?
Because Access doesn't _REALLY_ support transactions-- things get
halfway committed.
-Aaron
T
Tony Toews [MVP]
[email protected] said:You can _EASILY_ get corruption with a power outage using MS Access.
Can't you?
Power failures do not automatically or even easily mean corruption.
I've had clients which had 25 users in the database and had several
power failures over the years. While I was on scene and otherwise.
No corruptions.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
A
aaron.kempf
Honestly-- now _HOW_ does it work so that when the power goes out..
and 10 people have the DB open.. that it doesn't cause corruption?
-Aaron
and 10 people have the DB open.. that it doesn't cause corruption?
-Aaron
T
Tony Toews [MVP]
[email protected] said:Honestly-- now _HOW_ does it work so that when the power goes out..
and 10 people have the DB open.. that it doesn't cause corruption?
Because corruptions only happen when there is a failure of some sort
during that brief moment of time when Access/Jet is actually writing
to the file by either doing an append, delete or update. Access/Jet
sets a bit in the header when starting to do a write of some sort and
clears that bit when done.
Also the server was on a UPS which helped with the caching.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
C
Clif McIrvin
I'd vote for 'there's more behind her question."
I see a good discussion here already, that has many good things to
think about.
Try removing the reference to "Access 2007" from the question, ie. try
to answer "Why is it important to capture, record, and save
information?" and see where that takes you.
Access 2007 is simply a tool being used to do ..... what?
Enjoy your class, and learn much!
I see a good discussion here already, that has many good things to
think about.
Try removing the reference to "Access 2007" from the question, ie. try
to answer "Why is it important to capture, record, and save
information?" and see where that takes you.
Access 2007 is simply a tool being used to do ..... what?
Enjoy your class, and learn much!
A
a a r o n . k e m p f
good stuff.
So how many servers you got? how about desktops?
You gotta put UPS on them too- because your desktops have _SOME_
important data right?
-Aaron
So how many servers you got? how about desktops?
You gotta put UPS on them too- because your desktops have _SOME_
important data right?
-Aaron
T
Tony Toews [MVP]
You gotta put UPS on them too- because your desktops have _SOME_
important data right?
No, they shouldn't have any important data on the desktops. All that
data should be on the network.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
A
a a r o n . k e m p f
well.. Not sure that I agree with that. You are the master of the 3-
tier MDB right? Front End, Back End.. and oh yah a fucking TEMPDB
written in MDB?
ROFL
What a scam, dog
the point of the matter-- is that if someone is writing to a LOCAL
table-- when the power goes out-- they'll have corruption then right?
Sounds to me-- like troubleshooting corruption in TWO TIERS is a lot
harder than _ZERO_CORRUPTION_EVER_.
tier MDB right? Front End, Back End.. and oh yah a fucking TEMPDB
written in MDB?
ROFL
What a scam, dog
the point of the matter-- is that if someone is writing to a LOCAL
table-- when the power goes out-- they'll have corruption then right?
Sounds to me-- like troubleshooting corruption in TWO TIERS is a lot
harder than _ZERO_CORRUPTION_EVER_.