Access crash, save to Mypassword.mdb

[PACALA_BA]

start...MyData.mdb
( typing Mypassword to keyboardbuffer)
Logon - dialog for Mypassword
(retrieving Mypassword from keyboardbuffer)
--First Access crash on MyData.mdb (secure-MDW)
Report to Microsoft dialog
check-restart-YES
MyData_backup.mdb
starting...MyData.mdb
( typing Mypassword to keyboardbuffer)
--Second Access crash on MyData.mdb
MyData_backup.mdb....exists, then SaveAsFile dalog
(retrieving Mypassword from keyboardbuffer and saved to
**Mypassword.mdb**)
Logon - dialog for password
-------------------
if exists MyData_backup.mdb than save to MyData_backup_1.mdb,
and do not ask user for file name.....my opinion



----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...-9d91-00b8201f0296&dg=microsoft.public.access

 

[Larry Linson]

Even if English is not your native language, it would be helpful if you
attempted to write complete sentences, summarized what point you are trying
to make, and actually asked the question you want answered. And, most
certainly, if you are making a suggestion to Microsoft, as the text
indicates, you have to be clear as to what you are suggesting that Microsoft
_do_.

None of those are clear to me, and I am modestly successful at interpreting
English from non-native-English speakers, and have used Access daily since
January 1993.

Larry Linson
Microsoft Office Access MVP

 

[PACALA_BA]

Ok, in other words
After Access crash is created MyDatabase_backup.mdb
if FileExists(MyDatabase_backup.mdb) then
Open FileSaveAs Dialog
if Access-KeybordBuffer is empty then
Ask user for Destination Name.......OK
MyDatabase_backup_0001.mdb
MyDatabase_backup_0002.mdb
and so on,....would be more Better without this FileSaveAs Dialog
else
Save to MyPassword.mdb...WRONG
endif
else
Save to MyDatabase_backup.mdb...OK
end if

 

[Larry Linson]

Ok, in other words
After Access crash is created MyDatabase_backup.mdb

What, exactly, do you mean by "is created"? Is there something in your
database that creates a backup? Do you manually create a backup? Does the
system create a file by that name automatically? If the latter, is it part
of some greater process, part of running the program normally, part of your
error handling code?

What exactly do you mean by "Access crash"? What are the symptoms of
"crash" from your perspective? "Crash" is not a specific computing term...
it is used informally to describe a number of different kinds of occurrence.

Where and under what circumstances is the following code executed? Is it in
an error handling sequence identified in an On Error GoTo statement? Is it
in response to a specific user action, and, if so, what?

if FileExists(MyDatabase_backup.mdb) then

I assume you have the fully-qualified (aka "well-formed") path which you use
along with "MyDatabase_backup.mdb" to determine whether such a file exists
where you expect it to be.

Open FileSaveAs Dialog
if Access-KeybordBuffer is empty then

What is "Access-KeybordBuffer"? Is this a variable you have defined?

Ask user for Destination Name.......OK
MyDatabase_backup_0001.mdb
MyDatabase_backup_0002.mdb
and so on,....would be more Better without this FileSaveAs Dialog

Is there a reason that you cannot use the "Dir" function to determine the
existence of a file named "MyDatabase_backup.mdb" and/or similar names with
numeric characters appended? Is there a reason, if so, that you cannot
determine the largest number appended, and create the next one in sequence?

else

This else appears to indicate that you are either obtaining a new filename,
or saving, but not both...

Save to MyPassword.mdb...WRONG

Could you please explain what you mean by the immediately preceding line?
What would you be trying to accomplish by doing a save to MyPassword.mdb?
What, indeed, is "MyPassword.mdb"? What is it that you would be saving to
MyPassword.mdb? Why would it be "WRONG"?

endif

Should this be "end if"?

else
Save to MyDatabase_backup.mdb...OK

end if

In your example, you do not have complete logical structures for your
IF...THEN...ELSE... END IFs (at least, assuming, as I do, that the earlier
"endif" is intended to be "end if".
You are correct... it is not at all clear to me, as witness the questions I
have asked.

than try you to use and Crash Database,

Neither is this clear to me... what Database? "Use it," how? "Crash" it,
how?

that crashes not ONLY ONE-times....

And, I do not understand what you mean by this statement.

I'm sorry, but if we are not able to understand what you are writing about,
the probability of our being able to assist you is low or non-existent. As
it is, although you write a number of lines, all I can understand you to be
saying is, "Something went wrong somewhere. What do I do to correct it?"

Are there any appropriate newsgroups conducted in your native language? I
am quite certain, from seeing many of your posts and many responses, that we
are stumbling over a language barrier here -- we have just been unable to
determine the details of what you are trying to say. Please do not be
insulted, as I am certain that if I were trying to post an Access question
in some language other than English, it would be equally or more difficult
to interpret my question.

I also have seen a number of responses asking you if you have tried what you
are doing on a different computer, and I do not recall your saying that you
have. I strongly suggest that you do trying running the databases you are
having problems with on a different computer.

From my perspective... a "crash" would result in "the Blue Screen of Death",
bringing down the operating system, along with Access; or, at least, it
would result in an error (and an error message) when the operating system
shut down Access.

If we can, then once we do, understand what you are trying to describe, it
would be helpful to know the Version of Windows on which you are running,
what Service Packs have been applied AND the version of Office or Access you
are running and what Service Packs have been applied.

Regards,

Larry Linson
Microsoft Office Access MVP

 

[PACALA_BA]

Hi, This is ACCESS-XP CRASH
http://i37.tinypic.com/swu249.jpg
http://i35.tinypic.com/1zdslqa.jpg
http://i38.tinypic.com/wgz6w.jpg
this year over 100 access-2003-crashes reported to microsoft.....
-----------------------------------------------------Access-2003, menu-backup database
MyDatabase_2008-11-01.mdb
MyDatabase_2008-11-01(2).mdb
MyDatabase_2008-11-01(3).mdb
and so on , auomatic without asking user....thats all.

 

[Larry Linson]

You provided an answer to one of many specific questions I asked... that
answer is helpful in understanding what you mean by "crash". But it,
unfortunately, isn't helpful in diagnosing what is causing the problem.

If you could provide similarly clear answers to the other questions that I,
and others have asked, then perhaps someone can offer you some useful
suggestions. I really would not have bothered you with the additional
questions had I not thought that the answers might help us in diagnosing
your problem.

Again, I will suggest that you execute your database on some different PCs.
That is a start at diagnosing whether it is just a problem with software
setup or configuration of that one machine, or whether there is a more
general problem.

For your information, "reporting crashes to Microsoft" is not the same as
calling Microsoft support for tech support. They use those error reports
(sometimes also called memory dumps) to categorize the number and kind of
errors that users are encountering, not to diagnose and assist individual
users with their problem. Perhaps you were under the impression that
"reporting crashes" was requesting assistance from Microsoft tech support.
I note you have mentioned how many crashes you reported, in several of your
posts -- and, it occurred to me that you may have been under a
misunderstanding about the purpose and use of those error reports by
Microsoft.

Larry Linson
Microsoft Office Access MVP