Chinese/ strange characters

[Marco Silva]

Hi. I have a back-end and front-end solution in access.

As you may imagine, some users access to the same back-end database to
update data.

They don't usually use to update the same records.

My problem is that sometimes some records change what is written to a some
king of special characters.

It seems that it's chinese characters or something looked like.

I can I prevent this to happen?? because this makes me to delete that record
and of course the data that is into.

Regards,
Marco

 

[Jerry Whittle]

There's a very good chance that the database is corrupt. At times like this,
nothing beats a good backup. In fact make a complete backup of your database
now and put it away for safe keeping.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[PhotoFinish]

I have a similar problem, and I doubt the database is corrupt as such. I
have a reproducible problem -- I just can't figure out how to fix it. I have
a screen for users to edit records in a table. You go in, call up the
record, change what needs be, and close. Simple. You can also change two
fields that are stored in the table, but the source is from other tables, so
we make them click "change owner", e.g., and it takes them to another screen
where they can change owner. Then they return.
Routinely, we get "Write conflicts" when we return (we are using optimistic
locks), and most times when you say "Save it anyway", it is OK. But
sometimes, we don't get the error, but it cheerfully changes about half the
fields in the record to "Chinese". It also alters the record ID number,
which we don't let the users even see. If I call up the record, it comes up,
with the "Chinese", but I cannot delete it, because it says there is no index
matching the number, and clean database most often doesn't get rid of it.
But it will allow me to untimately delete the record.
I would rather a) it doesn't do that, or b) that it is easily recoverable,
and I don't have to kick users off, or come in at weird hours.

 

[PhotoFinish]

Marco,
I have been playing around with this and I found something interesting. If
you read my first reply, I mention that I get this when I update a portion of
a record via a form called by a form used to edit the record. I also
mentioned that we use "optimistic" locking, because we are a multi-user site,
with data in a back end.
Well, just for grins, in the "inner" form's properties, I set locking to
"Edited Records" (aka pesimestic locking). So far, when I make a change, and
return the the main edit form and make changes, I don't get the "write
conflict" error, but more importantly, so far I haven't generated any
"Chinese". So maybe Microsoft's optimistic locking has a bug!
(Imagine!).

 

[PhotoFinish]

Sorry. I lied. That didn't fix it. I just managed to break it. So I am
lost. I really don't want to change everything to "pesimestic", after all,
Access says that in a multi-user site to not use it. ARRRGGGGHHH!

 

[Marco]

Hello. Good that someone understand my problems.

I think that my database is not corruped. Almost shure.

I really don't know what to do. Times to times this happens. I think that is
because someone is trying to use the same record at the same times. But most
of the times they can do it. because this error is not regular.

I don't know what to do.

I'm trying to use the option in the forms option named Record Locks and I
using the option Edited Records.

I tried this blocks the records against double editing.

But I had the problem after again.

WHAT TO DO??????????

I think We should put this issue on Microsoft.

I'm with you my friend.

Regards,
Marco Silva

 

[Jerry Whittle]

I have little doubt that both you and PhotoFinish are experiencing database
corruption problems especially if the 'chinese' characters happen to be in a
memo field.

I suggest that both of you go to Tony Toews' and/or Allen Brown's web sites
and work through the corruption issues.