Discrepancy in dB size (Access 2000 vs XP)

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

Hi all,

I hope I'm posting this to the right forum. Please
forgive me if I'm not.

I've recently upgraded to Office XP, had issues using
Access XP with my file (created using 2000), then
reinstalled Access 2000.

In the interim, I've noticed that files compacted (done
automatically when file is closed) using XP are a little
bigger than HALF the size of when compacted using 2000.

Is this normal?

By the way, I did a search on the newsgroups
using 'compact' as my criteria. There was similar post on
October 16 by Jim titled " Error going from Access2000 to
XP". However, I could not find this message on any of the
boards to view responses and the search result didn't help
to narrow that down as all it stated was that it was on
microsoft.public.access.

Thanks for any and all help!
Chris
 
In the interim, I've noticed that files compacted (done
automatically when file is closed) using XP are a little
bigger than HALF the size of when compacted using 2000.

Is this normal?
Click to expand...

Not surprising, at any rate. A2000 was a particularly buggy version,
notorious for bloating and inefficient storage!

Note that XP allows you to work with databases in A2000 format, in
fact that's the default. What specific problems were you having with
XP?
 
Hi John,
Thanks for the info!

As for my problem with XP (I posted this on the Forms,
programming newsgroup but didn't get a response), let me
first describe what was supposed to happen with 2000.

1) Tech selects 'Test' from the switchboard
2) Dialogue opens prompting tech to select a product from
a combo box and enter a serial number into a control
3) Tech selects ok to open a data entry form
4) Form consists of main and sub form (changes depending
on the product chosen). Product name is passed to the
main form and the serial number is passed to the subform.

In XP, the appropriate sub-form does not open. Instead, I
get an error "-2147352567: You can't assign a value to
this object." . I know exactly what the offending line of
code is (frmCoCSub.SerialNum = Me.txtSerial) but I don't
understand WHY it occurs.

More info can be found in my Oct 6 post with subject
line "Form/subform issues"

Thanks!
 
1) Tech selects 'Test' from the switchboard
2) Dialogue opens prompting tech to select a product from
a combo box and enter a serial number into a control
3) Tech selects ok to open a data entry form
4) Form consists of main and sub form (changes depending
on the product chosen). Product name is passed to the
main form and the serial number is passed to the subform.

In XP, the appropriate sub-form does not open. Instead, I
get an error "-2147352567: You can't assign a value to
this object." . I know exactly what the offending line of
code is (frmCoCSub.SerialNum = Me.txtSerial) but I don't
understand WHY it occurs.
Click to expand...

Please post the relevant code snippet, and let us know what SerialNum
and txtSerial are and how they're related.
 
Hi John,

I'm afraid I can't post the code. It was work related and
I was laid off yesterday so I guess the point is probably
moot - unless it can help someone else.

All I can say is that frmCoCSub.SerialNum is the control
on the subform - obviously :) The data is then passed to
the appropriate product table.

Me.txtSerial is the control on the original dialogue from
which the tech selects the product and enters the serial
number.

Chris
 
Thanks John! With the way things are in the tech sector
I'm starting to think it's time to move on to something
else.
 
Back
Top