Good Morning, Mike:
Thanks for the clarification. Yes, I did notice, thus no response
from me until someone suggested to submit a bug. My reaction was to
get this cleared right away. Why fake news?
Having said that, if I remember correctly, and looking at our
records, my entire development team has spent many many hours to
address all your reported items related to R:BASE X Enterprise
(Version 10), including some cool enhancements. They provided you
with private updates, etc. for your testing and verification. Since
there were no further reports or any pending items for a long time, I
am just curious as to what is preventing you from taking advantage of
all those fixes and enhancements in R:BASE X Enterprise (Version 10),
and why you still continue to use the un-supported (EOS/EOL) version
of R:BASE 9.5 for your employer?
Remember, one of the most important aspects in business growth is
your company data, and no one else has more invested in your success
than R:BASE Technologies!
Please let us know if there is anything else we can do to help you.
Very Best R:egards,
Razzak
At 10:56 PM 6/15/2017, [email protected] wrote:
Good evening, Razzak:
With all due respect I did specify in my original post that I was
using eXtreme 9.5.
At 10:47 AM 6/14/2017, [email protected] wrote:
"Using eXtreme 9.5, I would appreciate some suggestions or insight
into why this happens or what I can look for."
At any rate, this particular problem has appeared sporadically over
the last couple of years with one particular database. It's a
relatively simple one with two tables and a few views. It's less
than 50MB in size.
I finally decided to post to the list for suggestions.
I have R:Styled and traced my programs and carefully examined the
code. No errors or issues were discovered.
I am going to design a different method for backing up the database
to see if I can eliminate the error.
I will share my findings.
Thank you for your comments and suggestions.
Kind Regards.
Mike Ramsour
AK Steel Coshocton Works
Quality Department
Phone: 740-829-4340
Cell: 740-502-1659
From: "A. Razzak Memon" <[email protected]>
To: [email protected],
Date: 06/15/2017 03:34 PM
Subject: Re: [RBASE-L] - Password error
Sent by: [email protected]
Mike,
Did you realize that everyone on this list thinks that you are using
R:BASE X Enterprise, when in fact, you are NOT.
Since you are still using R:BASE eXtreme 9.5 (64), is this the first
time you have encountered such -ERROR-?
What has changed on you end, as this has nothing to do with R:BASE,
since you have been using the same version for a long time, using the
same database.
Have you checked your backup databases?
Hope that provides you with some blue's clues ...
Razzak
At 10:47 AM 6/14/2017, [email protected] wrote:
>Good day:
>
>I have a daily backup routine that loops through about 20
>databases. The program connects to a database, AUTOCHKs it and then
>copies it to a backup folder.
>
>There is one database that generates the following error when the
>program attempts to connect to it: -ERROR- The current password is
>not correct for this user identifier. (2867)
>
>The owner of the database is set to public and there has never been
>a password associated with the database.
>
>Entering a bogus password or clicking through it generates this
>message: -ERROR- Incorrect password. User identifier has been
>changed to PUBLIC. (2870)
>
>After which the database gets backed up.
>
>I cannot find anything that would indicate why this is happening to
>this one particular database. I've checked it, I've rebuilt it and
>still I get the message.
>
>Using eXtreme 9.5, I would appreciate some suggestions or insight
>into why this happens or what I can look for.
>
>Thanks for any help.
--
You received this message because you are subscribed to the Google Groups
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
