By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,445 Members | 3,172 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,445 IT Pros & Developers. It's quick & easy.

Database twice as large after using password

P: n/a
Hi and Thanks in advance,

After inserting 3000 records into our database (MS Access 2000) the size is
17.3 MB. But if we use the User/ Group Permissions to secure our database,
the same 3000 records added will give us a size of 36.2 MB. What causes
such drastic overhead when using the permissions? The only time the
password is required is on startup, correct?
Again, thanks

Jordan
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
TC
Sorry, but there is no way that adding user/group permissions would be the
cause of that.

You must be doing something else different.

HTH,
TC
"Jordan @aongsi.ca>" <jordan.bruce<remove> wrote in message
news:Ve******************@news20.bellglobal.com...
Hi and Thanks in advance,

After inserting 3000 records into our database (MS Access 2000) the size is 17.3 MB. But if we use the User/ Group Permissions to secure our database, the same 3000 records added will give us a size of 36.2 MB. What causes
such drastic overhead when using the permissions? The only time the
password is required is on startup, correct?
Again, thanks

Jordan

Nov 12 '05 #2

P: n/a

"Jordan @aongsi.ca>" <jordan.bruce<remove> wrote in message
news:Ve******************@news20.bellglobal.com...
Hi and Thanks in advance,

After inserting 3000 records into our database (MS Access 2000) the size is 17.3 MB. But if we use the User/ Group Permissions to secure our database, the same 3000 records added will give us a size of 36.2 MB. What causes such drastic overhead when using the permissions? The only time the
password is required is on startup, correct?
Again, thanks

Jordan


Are these figures both after a compact? Various operations cause a
temporary bloat that can be retrieved by compacting.

I have never seen this sort of bloat due to securing a database. If you
used the security wizard it will by default encrypt the MDB which will
prevent it from being zipped or otherwise file squeezed but it shouldn't
double in size in its normal format.

The passwords are not stored in the database at all just the permissions
to the objects.

David
Nov 12 '05 #3

P: n/a
Are you using compact on exit?

"Jordan" <jordan.bruce<remove>@aongsi.ca> wrote in message news:<Ve******************@news20.bellglobal.com>. ..
Hi and Thanks in advance,

After inserting 3000 records into our database (MS Access 2000) the size is
17.3 MB. But if we use the User/ Group Permissions to secure our database,
the same 3000 records added will give us a size of 36.2 MB. What causes
such drastic overhead when using the permissions? The only time the
password is required is on startup, correct?
Again, thanks

Jordan

Nov 12 '05 #4

P: n/a
Yes we are compacting the database before and after the insertions, this is
why this problem seems to be so odd.

"Don Kuykendall" <sa*************@hotmail.com> wrote in message
news:59*************************@posting.google.co m...
Are you using compact on exit?

"Jordan" <jordan.bruce<remove>@aongsi.ca> wrote in message

news:<Ve******************@news20.bellglobal.com>. ..
Hi and Thanks in advance,

After inserting 3000 records into our database (MS Access 2000) the size is 17.3 MB. But if we use the User/ Group Permissions to secure our database, the same 3000 records added will give us a size of 36.2 MB. What causes
such drastic overhead when using the permissions? The only time the
password is required is on startup, correct?
Again, thanks

Jordan

Nov 12 '05 #5

P: n/a

"Jordan @aongsi.ca>" <jordan.bruce<remove> wrote in message
news:2u******************@news20.bellglobal.com...
Yes we are compacting the database before and after the insertions, this is why this problem seems to be so odd.

"Don Kuykendall" <sa*************@hotmail.com> wrote in message
news:59*************************@posting.google.co m...
Are you using compact on exit?

"Jordan" <jordan.bruce<remove>@aongsi.ca> wrote in message news:<Ve******************@news20.bellglobal.com>. ..
Hi and Thanks in advance,

After inserting 3000 records into our database (MS Access 2000) the size is
17.3 MB. But if we use the User/ Group Permissions to secure our database, the same 3000 records added will give us a size of 36.2 MB. What

causes such drastic overhead when using the permissions? The only time the
password is required is on startup, correct?
Again, thanks

Jordan



Sorry for the last post, we are not compacting the database after the
insertions because the insertions do not complete because we reach the size
limit.
Nov 12 '05 #6

P: n/a
TC

"Jordan @aongsi.ca>" <jordan.bruce<remove> wrote in message
news:OC******************@news20.bellglobal.com...

"Jordan @aongsi.ca>" <jordan.bruce<remove> wrote in message
news:2u******************@news20.bellglobal.com...
Yes we are compacting the database before and after the insertions, this is
why this problem seems to be so odd.

"Don Kuykendall" <sa*************@hotmail.com> wrote in message
news:59*************************@posting.google.co m...
Are you using compact on exit?

"Jordan" <jordan.bruce<remove>@aongsi.ca> wrote in message

news:<Ve******************@news20.bellglobal.com>. ..
> Hi and Thanks in advance,
>
> After inserting 3000 records into our database (MS Access 2000) the size
is
> 17.3 MB. But if we use the User/ Group Permissions to secure our

database,
> the same 3000 records added will give us a size of 36.2 MB. What

causes > such drastic overhead when using the permissions? The only time the
> password is required is on startup, correct?
>
>
> Again, thanks
>
> Jordan



Sorry for the last post, we are not compacting the database after the
insertions because the insertions do not complete because we reach the

size limit.


What size limit? 3000 records/36Mb is nowhere near any Access size limit!

TC

Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.