Encoding and Decoding

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm a novice and wanted to encode my database - then synchronize it with the
master on another pc. Do I just leave the database encoded and work in it
that way? Or do I encode it before shipping it for synchronization, but work
in it "decoded". Any help would be appreciated.

Thanks,

CC
 
CC, take a step back, pretend you are us - having absolutely zero
knowledge of what you are doing - then help us out with the following
info!

- What do you mean by "encode"?

- Why do you want to do that? What are you trying to achieve with it?

- How do you plan to "synchronize" your db with the other one? Do you
mean "replication"? Replication is a complex subject, not ontopic for
this newsgroup.

- Is any of this related to the Security aspects of Microsoft Access -
the actual topic of this newsgroup?

- Are you /using/ Microsoft Access?

TC
 
I am using Access and "Encode" is an option under Tools > Security is
Encode/Decode. Apparently, it's a way to compact your database and make it
unreadable by a word processor and is a good thing to do should you be using
removable media to store your database. I'm trying to achieve some level of
protection in case I have to email my database.

So, I'm wondering, if I encode my database, do I then continue to work with
it encoded or do I have to decode it when I go to synch it with the master?

does that help clarify? Thanks,

CC
 
If I remember correctly, in earlier versions of Access, this feature was
called 'encryption' rather than 'encoding'. I'd guess that a lot of people
are probably more familiar with the old terminology.

Access automatically decrypts/decodes an encrypted/encoded database when you
open it in Access. If you're using Replication, I expect that the process is
probably automatic as well, but you might want to ask in the Replication
newsgroup - as TC says, Replication is a specialised subject.
 
Ok, as Brendon said, it used to be called encryption.

Understand that Access encryption is /NOT/ used for the normal purpose
of encryption - namely, to stop people reading the data unless that
have the proper key. Access encryption is only used to stop people
altering the database file directly using a disk editor. But it does
not stop someone reading or changing the data /with Access/, because
Access will decrypt the data on reading, and encrypt it on writing,
automagically, "behind the scenes".

So, it really does not matter whether you encrypt your database, or
not. Unless it has been /secured/ using Access user-level security,
anyone will be able to open it, using any copy of Access, and alter
data as they wish.

HTH,
TC
 
OK. So it looks like encoding is not sufficient. Thanks for the
clarification. So, I run the user level security wizard and everything
appears OK. I set myself to the Admin group as well as the Full Permissions
and Full Data group, and Finish the wizard, no problem. But when I try to
open the database I get:

"You do not have the necessary permissions to use the <name> object. Have
your system administrator or the person who created this object establish the
appropriate permissions for you. (Error 3033)
You do not have the necessary permissions for the specified object. To
change your permission assignments, see your system administrator or the
object's creator."

I got this message, even when I created a new test database from scratch.
Also, this is a "Design Master" becaues I do need to replicate my database. I
don't know if this makes a difference. Thanks again.
 
FRIGGIN' GOOGLE! I just did a long answer & hit send. Google replied
"Server Error", & threw the lot away! So here is an abridged version of
what I wanted to say.

Replication is a complex topic. I know very little about it, so I can
not comment on what you are planning. However, I do know that people
often try to use it in ways that /seem/ sensible, but in fact, will
cause many problems down the track. I strongly recommend that you
compose a short but detailed description of what you are planning to
do, then post it to microsoft.public.access.replication, & ask for
comment there.

HTH,
TC
 
Ouch!

First, I know nothing about replication. It's a very complex topic,
worhty of a seperate newsgroup: microsoft.public.access.replication, or
somesuch. I strongly suggest that you compose a short but detailed
post, describing exactly what you are planning to do, and then post
there, asking if your plans are ok. Seriously, I know that people try
to do certain things with replication, which are guaranteed to cause
confusing problems down the track. Check with the experts, that what
you are planning to do, is ok; particularly in regard to whether it
will work when the db is secured, or not.

As for the security problem, my advice is always this: you need to
follow an explicit list of written instructions - adding & omitting
nothing. IMHO, it's too hard to get it right by messing around, or just
using the wizard. Try the Access Security FAQ, often referenced in this
newsgroup.

HTH,
TC
 
Back
Top