Unusual Behavior with Database

Create a new database (MDB presumably, not ACCDB.)
Then import everything from the old one.

You may find that some things don't import correctly, but you should be able
to get most of your data.

Post a reply to this thread if you get stuck part way through the process.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Handy Matt" <Handy Matt DeleteThis @discussions.microsoft.com> wrote in message
news:CE1175F1-8C69-4106-A013-A0C7AFE6B9D6@microsoft.com...
>I run Windows using Parallels Desktop on my iMac. Several weeks ago there
> was a brief power outage at home and ever since then I've had problems
> with
> my Access database. I run Access 2007 but my database is version 2003. I
> first experienced a duplicate record in my database. I believe I have
> taken
> care of that problem. Most recently my database closed due to a Microsoft
> problem. It created a backup file and started a compress cycle. That went
> on
> and on and on. I hit the ESC key to halt the process. My file went from
> 36
> megabyte to 2.07 gigabyte. That process was repeated a second time a day
> or
> two later. I let the compress / repair cycle run for over 2 hours and
> again
> hit the ESC key. The file once again was 2.07 gigabyte.
>
> I've also received 2 error messages. One stated "You do not have
> necessary
> permission to use the HandyMatt.mdb object". A second message said
> "Records
> cannot be read; no permission on MsysAccessObjects".
>
> I use this database to maintain all my customer information. I haven't
> been
> able to update it because of these occurrences. Any ideas as to what is
> happening?
>
> Handy Matt
 >> Stay informed about: Unusual Behavior with Database 

I appreciate the responses I received. Thank you. I was curious about the
things that may not import correctly. What types of things might those be?
I want to be prepared so I know what to look for. Now the fun begins. I
will give a progress update when I get things started, or let you know if
there's a problem I encounter.

"Allen Browne" wrote:

> Create a new database (MDB presumably, not ACCDB.)
> Then import everything from the old one.
>
> You may find that some things don't import correctly, but you should be able
> to get most of your data.
>
> Post a reply to this thread if you get stuck part way through the process.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Handy Matt" <Handy Matt RemoveThis @discussions.microsoft.com> wrote in message
> news:CE1175F1-8C69-4106-A013-A0C7AFE6B9D6@microsoft.com...
> >I run Windows using Parallels Desktop on my iMac. Several weeks ago there
> > was a brief power outage at home and ever since then I've had problems
> > with
> > my Access database. I run Access 2007 but my database is version 2003. I
> > first experienced a duplicate record in my database. I believe I have
> > taken
> > care of that problem. Most recently my database closed due to a Microsoft
> > problem. It created a backup file and started a compress cycle. That went
> > on
> > and on and on. I hit the ESC key to halt the process. My file went from
> > 36
> > megabyte to 2.07 gigabyte. That process was repeated a second time a day
> > or
> > two later. I let the compress / repair cycle run for over 2 hours and
> > again
> > hit the ESC key. The file once again was 2.07 gigabyte.
> >
> > I've also received 2 error messages. One stated "You do not have
> > necessary
> > permission to use the HandyMatt.mdb object". A second message said
> > "Records
> > cannot be read; no permission on MsysAccessObjects".
> >
> > I use this database to maintain all my customer information. I haven't
> > been
> > able to update it because of these occurrences. Any ideas as to what is
> > happening?
> >
> > Handy Matt
>
>
 >> Stay informed about: Unusual Behavior with Database 

A corrupt form may not import. Chances are it will notify you if it can't be
imported.

For general guidance on converting to Access 2007 from previous versions,
see:
http://allenbrowne.com/Access2007.html

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Handy Matt" <HandyMatt DeleteThis @discussions.microsoft.com> wrote in message
news:A3A179DC-85FC-4DB4-B9BD-6E29531D5131@microsoft.com...
>I appreciate the responses I received. Thank you. I was curious about the
> things that may not import correctly. What types of things might those
> be?
> I want to be prepared so I know what to look for. Now the fun begins. I
> will give a progress update when I get things started, or let you know if
> there's a problem I encounter.
>
> "Allen Browne" wrote:
>
>> Create a new database (MDB presumably, not ACCDB.)
>> Then import everything from the old one.
>>
>> You may find that some things don't import correctly, but you should be
>> able
>> to get most of your data.
>>
>> Post a reply to this thread if you get stuck part way through the
>> process.
>>
>> "Handy Matt" <Handy Matt DeleteThis @discussions.microsoft.com> wrote in message
>> news:CE1175F1-8C69-4106-A013-A0C7AFE6B9D6@microsoft.com...
>> >I run Windows using Parallels Desktop on my iMac. Several weeks ago
>> >there
>> > was a brief power outage at home and ever since then I've had problems
>> > with
>> > my Access database. I run Access 2007 but my database is version 2003.
>> > I
>> > first experienced a duplicate record in my database. I believe I have
>> > taken
>> > care of that problem. Most recently my database closed due to a
>> > Microsoft
>> > problem. It created a backup file and started a compress cycle. That
>> > went
>> > on
>> > and on and on. I hit the ESC key to halt the process. My file went
>> > from
>> > 36
>> > megabyte to 2.07 gigabyte. That process was repeated a second time a
>> > day
>> > or
>> > two later. I let the compress / repair cycle run for over 2 hours and
>> > again
>> > hit the ESC key. The file once again was 2.07 gigabyte.
>> >
>> > I've also received 2 error messages. One stated "You do not have
>> > necessary
>> > permission to use the HandyMatt.mdb object". A second message said
>> > "Records
>> > cannot be read; no permission on MsysAccessObjects".
>> >
>> > I use this database to maintain all my customer information. I haven't
>> > been
>> > able to update it because of these occurrences. Any ideas as to what
>> > is
>> > happening?
 >> Stay informed about: Unusual Behavior with Database 

I completed constructing new tables and forms from scratch in a new database.
I did not import any of the old database's items. Today I imported one
table from my old database to my new database. Then I ran an append query to
transfer the records from the old table to the new table. I noticed some
date fields within specific records were completely filled with the pound
sign (############). When I tried to correct the field by typing in the new
date, or selecting it from the calendar icon, the field returned all pound
signs, even though it would indicate the correct date when I would select
that field. On a few occasions I was able to get the actual date to appear
in long date format. When I closed the table and opened it again, the
corrected date was once again all pound signs. I sorted my table by date and
found that all the dates in this table that happen to be any Wednesday in the
month of September for the 5 years I've input are those that are appearing
this way. For example, 09.08.04, 09.21.05, 09.13.06, 09.05.07, & 09.24.08.
Very peculiar. I deleted one of these records and input all my information
as a new record. The date in the new record came back with all pound signs.
What's going on?

"Allen Browne" wrote:

> A corrupt form may not import. Chances are it will notify you if it can't be
> imported.
>
> For general guidance on converting to Access 2007 from previous versions,
> see:
> http://allenbrowne.com/Access2007.html
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Handy Matt" <HandyMatt.RemoveThis@discussions.microsoft.com> wrote in message
> news:A3A179DC-85FC-4DB4-B9BD-6E29531D5131@microsoft.com...
> >I appreciate the responses I received. Thank you. I was curious about the
> > things that may not import correctly. What types of things might those
> > be?
> > I want to be prepared so I know what to look for. Now the fun begins. I
> > will give a progress update when I get things started, or let you know if
> > there's a problem I encounter.
> >
> > "Allen Browne" wrote:
> >
> >> Create a new database (MDB presumably, not ACCDB.)
> >> Then import everything from the old one.
> >>
> >> You may find that some things don't import correctly, but you should be
> >> able
> >> to get most of your data.
> >>
> >> Post a reply to this thread if you get stuck part way through the
> >> process.
> >>
> >> "Handy Matt" <Handy Matt.RemoveThis@discussions.microsoft.com> wrote in message
> >> news:CE1175F1-8C69-4106-A013-A0C7AFE6B9D6@microsoft.com...
> >> >I run Windows using Parallels Desktop on my iMac. Several weeks ago
> >> >there
> >> > was a brief power outage at home and ever since then I've had problems
> >> > with
> >> > my Access database. I run Access 2007 but my database is version 2003.
> >> > I
> >> > first experienced a duplicate record in my database. I believe I have
> >> > taken
> >> > care of that problem. Most recently my database closed due to a
> >> > Microsoft
> >> > problem. It created a backup file and started a compress cycle. That
> >> > went
> >> > on
> >> > and on and on. I hit the ESC key to halt the process. My file went
> >> > from
> >> > 36
> >> > megabyte to 2.07 gigabyte. That process was repeated a second time a
> >> > day
> >> > or
> >> > two later. I let the compress / repair cycle run for over 2 hours and
> >> > again
> >> > hit the ESC key. The file once again was 2.07 gigabyte.
> >> >
> >> > I've also received 2 error messages. One stated "You do not have
> >> > necessary
> >> > permission to use the HandyMatt.mdb object". A second message said
> >> > "Records
> >> > cannot be read; no permission on MsysAccessObjects".
> >> >
> >> > I use this database to maintain all my customer information. I haven't
> >> > been
> >> > able to update it because of these occurrences. Any ideas as to what
> >> > is
> >> > happening?
>
>
 >> Stay informed about: Unusual Behavior with Database 

Pound sign just means column is to narrow to display all the info. Make
column bigger or change format from long date to a shorter version table
design.
"Handy Matt" <HandyMatt.DeleteThis@discussions.microsoft.com> wrote in message
news:61C2D2CB-F97C-4D72-B567-2F526227527D@microsoft.com...
>I completed constructing new tables and forms from scratch in a new
>database.
> I did not import any of the old database's items. Today I imported one
> table from my old database to my new database. Then I ran an append query
> to
> transfer the records from the old table to the new table. I noticed some
> date fields within specific records were completely filled with the pound
> sign (############). When I tried to correct the field by typing in the
> new
> date, or selecting it from the calendar icon, the field returned all pound
> signs, even though it would indicate the correct date when I would select
> that field. On a few occasions I was able to get the actual date to
> appear
> in long date format. When I closed the table and opened it again, the
> corrected date was once again all pound signs. I sorted my table by date
> and
> found that all the dates in this table that happen to be any Wednesday in
> the
> month of September for the 5 years I've input are those that are appearing
> this way. For example, 09.08.04, 09.21.05, 09.13.06, 09.05.07, &
> 09.24.08.
> Very peculiar. I deleted one of these records and input all my
> information
> as a new record. The date in the new record came back with all pound
> signs.
> What's going on?
>
> "Allen Browne" wrote:
>
>> A corrupt form may not import. Chances are it will notify you if it can't
>> be
>> imported.
>>
>> For general guidance on converting to Access 2007 from previous versions,
>> see:
>> http://allenbrowne.com/Access2007.html
>>
>> --
>> Allen Browne - Microsoft MVP. Perth, Western Australia
>> Tips for Access users - http://allenbrowne.com/tips.html
>> Reply to group, rather than allenbrowne at mvps dot org.
>>
>> "Handy Matt" <HandyMatt.DeleteThis@discussions.microsoft.com> wrote in message
>> news:A3A179DC-85FC-4DB4-B9BD-6E29531D5131@microsoft.com...
>> >I appreciate the responses I received. Thank you. I was curious about
>> >the
>> > things that may not import correctly. What types of things might those
>> > be?
>> > I want to be prepared so I know what to look for. Now the fun begins.
>> > I
>> > will give a progress update when I get things started, or let you know
>> > if
>> > there's a problem I encounter.
>> >
>> > "Allen Browne" wrote:
>> >
>> >> Create a new database (MDB presumably, not ACCDB.)
>> >> Then import everything from the old one.
>> >>
>> >> You may find that some things don't import correctly, but you should
>> >> be
>> >> able
>> >> to get most of your data.
>> >>
>> >> Post a reply to this thread if you get stuck part way through the
>> >> process.
>> >>
>> >> "Handy Matt" <Handy Matt.DeleteThis@discussions.microsoft.com> wrote in message
>> >> news:CE1175F1-8C69-4106-A013-A0C7AFE6B9D6@microsoft.com...
>> >> >I run Windows using Parallels Desktop on my iMac. Several weeks ago
>> >> >there
>> >> > was a brief power outage at home and ever since then I've had
>> >> > problems
>> >> > with
>> >> > my Access database. I run Access 2007 but my database is version
>> >> > 2003.
>> >> > I
>> >> > first experienced a duplicate record in my database. I believe I
>> >> > have
>> >> > taken
>> >> > care of that problem. Most recently my database closed due to a
>> >> > Microsoft
>> >> > problem. It created a backup file and started a compress cycle.
>> >> > That
>> >> > went
>> >> > on
>> >> > and on and on. I hit the ESC key to halt the process. My file went
>> >> > from
>> >> > 36
>> >> > megabyte to 2.07 gigabyte. That process was repeated a second time
>> >> > a
>> >> > day
>> >> > or
>> >> > two later. I let the compress / repair cycle run for over 2 hours
>> >> > and
>> >> > again
>> >> > hit the ESC key. The file once again was 2.07 gigabyte.
>> >> >
>> >> > I've also received 2 error messages. One stated "You do not have
>> >> > necessary
>> >> > permission to use the HandyMatt.mdb object". A second message said
>> >> > "Records
>> >> > cannot be read; no permission on MsysAccessObjects".
>> >> >
>> >> > I use this database to maintain all my customer information. I
>> >> > haven't
>> >> > been
>> >> > able to update it because of these occurrences. Any ideas as to
>> >> > what
>> >> > is
>> >> > happening?
>>
>>
 >> Stay informed about: Unusual Behavior with Database 

Not the brightest move on my part. It was the column width. I am making
progress with getting the new database up and running. I imported the most
important portion of my data and that all appears to be in good shape. I
believe I can see light at the end of the tunnel. Thank you.

"Pete D." wrote:

> Pound sign just means column is to narrow to display all the info. Make
> column bigger or change format from long date to a shorter version table
> design.
> "Handy Matt" <HandyMatt.RemoveThis@discussions.microsoft.com> wrote in message
> news:61C2D2CB-F97C-4D72-B567-2F526227527D@microsoft.com...
> >I completed constructing new tables and forms from scratch in a new
> >database.
> > I did not import any of the old database's items. Today I imported one
> > table from my old database to my new database. Then I ran an append query
> > to
> > transfer the records from the old table to the new table. I noticed some
> > date fields within specific records were completely filled with the pound
> > sign (############). When I tried to correct the field by typing in the
> > new
> > date, or selecting it from the calendar icon, the field returned all pound
> > signs, even though it would indicate the correct date when I would select
> > that field. On a few occasions I was able to get the actual date to
> > appear
> > in long date format. When I closed the table and opened it again, the
> > corrected date was once again all pound signs. I sorted my table by date
> > and
> > found that all the dates in this table that happen to be any Wednesday in
> > the
> > month of September for the 5 years I've input are those that are appearing
> > this way. For example, 09.08.04, 09.21.05, 09.13.06, 09.05.07, &
> > 09.24.08.
> > Very peculiar. I deleted one of these records and input all my
> > information
> > as a new record. The date in the new record came back with all pound
> > signs.
> > What's going on?
> >
> > "Allen Browne" wrote:
> >
> >> A corrupt form may not import. Chances are it will notify you if it can't
> >> be
> >> imported.
> >>
> >> For general guidance on converting to Access 2007 from previous versions,
> >> see:
> >> http://allenbrowne.com/Access2007.html
> >>
> >> --
> >> Allen Browne - Microsoft MVP. Perth, Western Australia
> >> Tips for Access users - http://allenbrowne.com/tips.html
> >> Reply to group, rather than allenbrowne at mvps dot org.
> >>
> >> "Handy Matt" <HandyMatt.RemoveThis@discussions.microsoft.com> wrote in message
> >> news:A3A179DC-85FC-4DB4-B9BD-6E29531D5131@microsoft.com...
> >> >I appreciate the responses I received. Thank you. I was curious about
> >> >the
> >> > things that may not import correctly. What types of things might those
> >> > be?
> >> > I want to be prepared so I know what to look for. Now the fun begins.
> >> > I
> >> > will give a progress update when I get things started, or let you know
> >> > if
> >> > there's a problem I encounter.
> >> >
> >> > "Allen Browne" wrote:
> >> >
> >> >> Create a new database (MDB presumably, not ACCDB.)
> >> >> Then import everything from the old one.
> >> >>
> >> >> You may find that some things don't import correctly, but you should
> >> >> be
> >> >> able
> >> >> to get most of your data.
> >> >>
> >> >> Post a reply to this thread if you get stuck part way through the
> >> >> process.
> >> >>
> >> >> "Handy Matt" <Handy Matt.RemoveThis@discussions.microsoft.com> wrote in message
> >> >> news:CE1175F1-8C69-4106-A013-A0C7AFE6B9D6@microsoft.com...
> >> >> >I run Windows using Parallels Desktop on my iMac. Several weeks ago
> >> >> >there
> >> >> > was a brief power outage at home and ever since then I've had
> >> >> > problems
> >> >> > with
> >> >> > my Access database. I run Access 2007 but my database is version
> >> >> > 2003.
> >> >> > I
> >> >> > first experienced a duplicate record in my database. I believe I
> >> >> > have
> >> >> > taken
> >> >> > care of that problem. Most recently my database closed due to a
> >> >> > Microsoft
> >> >> > problem. It created a backup file and started a compress cycle.
> >> >> > That
> >> >> > went
> >> >> > on
> >> >> > and on and on. I hit the ESC key to halt the process. My file went
> >> >> > from
> >> >> > 36
> >> >> > megabyte to 2.07 gigabyte. That process was repeated a second time
> >> >> > a
> >> >> > day
> >> >> > or
> >> >> > two later. I let the compress / repair cycle run for over 2 hours
> >> >> > and
> >> >> > again
> >> >> > hit the ESC key. The file once again was 2.07 gigabyte.
> >> >> >
> >> >> > I've also received 2 error messages. One stated "You do not have
> >> >> > necessary
> >> >> > permission to use the HandyMatt.mdb object". A second message said
> >> >> > "Records
> >> >> > cannot be read; no permission on MsysAccessObjects".
> >> >> >
> >> >> > I use this database to maintain all my customer information. I
> >> >> > haven't
> >> >> > been
> >> >> > able to update it because of these occurrences. Any ideas as to
> >> >> > what
> >> >> > is
> >> >> > happening?
> >>
> >>
>
>
>
 >> Stay informed about: Unusual Behavior with Database