PC Review


Reply
Thread Tools Rate Thread

Database shuts down when switch from design to form view

 
 
=?Utf-8?B?TmljayBY?=
Guest
Posts: n/a
 
      22nd Feb 2006
Hi all,
I have about 6 or 7 databases that I work on regularly. I just created a
new database in Access '02 from the ground up (it's still in production and
not being used widely - 1 user and me). When I am doing design changes and
go to switch to Form view the database craps out, shutdown, creates a back-up
and restarts and repairs itself. This has happened several times and I don't
want this to be an issue when I go to a wide release.
I am running this as a front-end/back-end with the user using an .mde file.
So far I haven't gotten any complaints about corruption from the user, but
she only has limited contact. Most of the data has been imported from excel
and manipulated using queries. I haven't had this problem with previous
databases, most of which were or are 2000 format. Is this a problem with
this particular database or has my copy of Access been corrupted?

All help would be greatly appreciated.
Thanks in advance,
NickX
 
Reply With Quote
 
 
 
 
=?Utf-8?B?WWlzTWFu?=
Guest
Posts: n/a
 
      22nd Feb 2006
hooray!
that makes two of us
after i used acc2003 for a few months i started having the same problem, but
actually when switching to design view. then it started whenever i did save
as in design view or when i did compile, noting helped until i made a
complede office reinstallation (i foolishly forgot to try system resore which
is a pretty powerful tool).

anyway after a few months i got it again and did the same

since sp2 the symptoms are less common (by me,at least)
--
Thankfully, YisMan


"Nick X" wrote:

> Hi all,
> I have about 6 or 7 databases that I work on regularly. I just created a
> new database in Access '02 from the ground up (it's still in production and
> not being used widely - 1 user and me). When I am doing design changes and
> go to switch to Form view the database craps out, shutdown, creates a back-up
> and restarts and repairs itself. This has happened several times and I don't
> want this to be an issue when I go to a wide release.
> I am running this as a front-end/back-end with the user using an .mde file.
> So far I haven't gotten any complaints about corruption from the user, but
> she only has limited contact. Most of the data has been imported from excel
> and manipulated using queries. I haven't had this problem with previous
> databases, most of which were or are 2000 format. Is this a problem with
> this particular database or has my copy of Access been corrupted?
>
> All help would be greatly appreciated.
> Thanks in advance,
> NickX

 
Reply With Quote
 
=?Utf-8?B?TmljayBY?=
Guest
Posts: n/a
 
      23rd Feb 2006
Thanks,
That's great, but that is the last resort. To re-install Access involves
calling the IT department, putting in a request, waiting three weeks, calling
IT back to put in another request because they can't find where I put in the
first request... (loop). So, as you can see, if I have to keep dumping and
loading Access I will never get anything done. Is there anyone out there
with an answer better than "Reboot" or "Dump and Load". I am on BackUp #12
since I started counting. Thank you for the effort YisMan. It is
appreciated.

Nick X

"YisMan" wrote:

> hooray!
> that makes two of us
> after i used acc2003 for a few months i started having the same problem, but
> actually when switching to design view. then it started whenever i did save
> as in design view or when i did compile, noting helped until i made a
> complede office reinstallation (i foolishly forgot to try system resore which
> is a pretty powerful tool).
>
> anyway after a few months i got it again and did the same
>
> since sp2 the symptoms are less common (by me,at least)
> --
> Thankfully, YisMan
>
>
> "Nick X" wrote:
>
> > Hi all,
> > I have about 6 or 7 databases that I work on regularly. I just created a
> > new database in Access '02 from the ground up (it's still in production and
> > not being used widely - 1 user and me). When I am doing design changes and
> > go to switch to Form view the database craps out, shutdown, creates a back-up
> > and restarts and repairs itself. This has happened several times and I don't
> > want this to be an issue when I go to a wide release.
> > I am running this as a front-end/back-end with the user using an .mde file.
> > So far I haven't gotten any complaints about corruption from the user, but
> > she only has limited contact. Most of the data has been imported from excel
> > and manipulated using queries. I haven't had this problem with previous
> > databases, most of which were or are 2000 format. Is this a problem with
> > this particular database or has my copy of Access been corrupted?
> >
> > All help would be greatly appreciated.
> > Thanks in advance,
> > NickX

 
Reply With Quote
 
=?Utf-8?B?TmljayBY?=
Guest
Posts: n/a
 
      23rd Feb 2006
Backup13

"Nick X" wrote:

> Thanks,
> That's great, but that is the last resort. To re-install Access involves
> calling the IT department, putting in a request, waiting three weeks, calling
> IT back to put in another request because they can't find where I put in the
> first request... (loop). So, as you can see, if I have to keep dumping and
> loading Access I will never get anything done. Is there anyone out there
> with an answer better than "Reboot" or "Dump and Load". I am on BackUp #12
> since I started counting. Thank you for the effort YisMan. It is
> appreciated.
>
> Nick X
>
> "YisMan" wrote:
>
> > hooray!
> > that makes two of us
> > after i used acc2003 for a few months i started having the same problem, but
> > actually when switching to design view. then it started whenever i did save
> > as in design view or when i did compile, noting helped until i made a
> > complede office reinstallation (i foolishly forgot to try system resore which
> > is a pretty powerful tool).
> >
> > anyway after a few months i got it again and did the same
> >
> > since sp2 the symptoms are less common (by me,at least)
> > --
> > Thankfully, YisMan
> >
> >
> > "Nick X" wrote:
> >
> > > Hi all,
> > > I have about 6 or 7 databases that I work on regularly. I just created a
> > > new database in Access '02 from the ground up (it's still in production and
> > > not being used widely - 1 user and me). When I am doing design changes and
> > > go to switch to Form view the database craps out, shutdown, creates a back-up
> > > and restarts and repairs itself. This has happened several times and I don't
> > > want this to be an issue when I go to a wide release.
> > > I am running this as a front-end/back-end with the user using an .mde file.
> > > So far I haven't gotten any complaints about corruption from the user, but
> > > she only has limited contact. Most of the data has been imported from excel
> > > and manipulated using queries. I haven't had this problem with previous
> > > databases, most of which were or are 2000 format. Is this a problem with
> > > this particular database or has my copy of Access been corrupted?
> > >
> > > All help would be greatly appreciated.
> > > Thanks in advance,
> > > NickX

 
Reply With Quote
 
=?Utf-8?B?WWlzTWFu?=
Guest
Posts: n/a
 
      23rd Feb 2006
sorry nick,in the ecstasy i simply forgot something else i do sometimes (do
in the present tense!) make a new database file>new completely new then
import all the db objects.
sometimes i manajed to import all at a time and it woked like brand new,
sometimes i imported all tables , closed and reopened imported queries,
closed...
etc.

great luck.
--
Thankfully, YisMan


"Nick X" wrote:

> Backup13
>
> "Nick X" wrote:
>
> > Thanks,
> > That's great, but that is the last resort. To re-install Access involves
> > calling the IT department, putting in a request, waiting three weeks, calling
> > IT back to put in another request because they can't find where I put in the
> > first request... (loop). So, as you can see, if I have to keep dumping and
> > loading Access I will never get anything done. Is there anyone out there
> > with an answer better than "Reboot" or "Dump and Load". I am on BackUp #12
> > since I started counting. Thank you for the effort YisMan. It is
> > appreciated.
> >
> > Nick X
> >
> > "YisMan" wrote:
> >
> > > hooray!
> > > that makes two of us
> > > after i used acc2003 for a few months i started having the same problem, but
> > > actually when switching to design view. then it started whenever i did save
> > > as in design view or when i did compile, noting helped until i made a
> > > complede office reinstallation (i foolishly forgot to try system resore which
> > > is a pretty powerful tool).
> > >
> > > anyway after a few months i got it again and did the same
> > >
> > > since sp2 the symptoms are less common (by me,at least)
> > > --
> > > Thankfully, YisMan
> > >
> > >
> > > "Nick X" wrote:
> > >
> > > > Hi all,
> > > > I have about 6 or 7 databases that I work on regularly. I just created a
> > > > new database in Access '02 from the ground up (it's still in production and
> > > > not being used widely - 1 user and me). When I am doing design changes and
> > > > go to switch to Form view the database craps out, shutdown, creates a back-up
> > > > and restarts and repairs itself. This has happened several times and I don't
> > > > want this to be an issue when I go to a wide release.
> > > > I am running this as a front-end/back-end with the user using an .mde file.
> > > > So far I haven't gotten any complaints about corruption from the user, but
> > > > she only has limited contact. Most of the data has been imported from excel
> > > > and manipulated using queries. I haven't had this problem with previous
> > > > databases, most of which were or are 2000 format. Is this a problem with
> > > > this particular database or has my copy of Access been corrupted?
> > > >
> > > > All help would be greatly appreciated.
> > > > Thanks in advance,
> > > > NickX

 
Reply With Quote
 
=?Utf-8?B?TmljayBY?=
Guest
Posts: n/a
 
      23rd Feb 2006
Thanks, I found a good answer with this title:

Converting from Access 2000 to Access 2002
In: microsoft.public.access.conversion

Now my database works great!
Thanks,
NickX

"YisMan" wrote:

> sorry nick,in the ecstasy i simply forgot something else i do sometimes (do
> in the present tense!) make a new database file>new completely new then
> import all the db objects.
> sometimes i manajed to import all at a time and it woked like brand new,
> sometimes i imported all tables , closed and reopened imported queries,
> closed...
> etc.
>
> great luck.
> --
> Thankfully, YisMan
>
>
> "Nick X" wrote:
>
> > Backup13
> >
> > "Nick X" wrote:
> >
> > > Thanks,
> > > That's great, but that is the last resort. To re-install Access involves
> > > calling the IT department, putting in a request, waiting three weeks, calling
> > > IT back to put in another request because they can't find where I put in the
> > > first request... (loop). So, as you can see, if I have to keep dumping and
> > > loading Access I will never get anything done. Is there anyone out there
> > > with an answer better than "Reboot" or "Dump and Load". I am on BackUp #12
> > > since I started counting. Thank you for the effort YisMan. It is
> > > appreciated.
> > >
> > > Nick X
> > >
> > > "YisMan" wrote:
> > >
> > > > hooray!
> > > > that makes two of us
> > > > after i used acc2003 for a few months i started having the same problem, but
> > > > actually when switching to design view. then it started whenever i did save
> > > > as in design view or when i did compile, noting helped until i made a
> > > > complede office reinstallation (i foolishly forgot to try system resore which
> > > > is a pretty powerful tool).
> > > >
> > > > anyway after a few months i got it again and did the same
> > > >
> > > > since sp2 the symptoms are less common (by me,at least)
> > > > --
> > > > Thankfully, YisMan
> > > >
> > > >
> > > > "Nick X" wrote:
> > > >
> > > > > Hi all,
> > > > > I have about 6 or 7 databases that I work on regularly. I just created a
> > > > > new database in Access '02 from the ground up (it's still in production and
> > > > > not being used widely - 1 user and me). When I am doing design changes and
> > > > > go to switch to Form view the database craps out, shutdown, creates a back-up
> > > > > and restarts and repairs itself. This has happened several times and I don't
> > > > > want this to be an issue when I go to a wide release.
> > > > > I am running this as a front-end/back-end with the user using an .mde file.
> > > > > So far I haven't gotten any complaints about corruption from the user, but
> > > > > she only has limited contact. Most of the data has been imported from excel
> > > > > and manipulated using queries. I haven't had this problem with previous
> > > > > databases, most of which were or are 2000 format. Is this a problem with
> > > > > this particular database or has my copy of Access been corrupted?
> > > > >
> > > > > All help would be greatly appreciated.
> > > > > Thanks in advance,
> > > > > NickX

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: Open A Specified Form In Another Database In Design View Lord Kelvan Microsoft Access Forms 3 13th Oct 2008 08:32 AM
Re: Open A Specified Form In Another Database In Design View Lord Kelvan Microsoft Access Form Coding 1 10th Oct 2008 08:40 AM
Re: Open A Specified Form In Another Database In Design View fredg Microsoft Access 0 9th Oct 2008 12:52 AM
Database Locking when going to form design view =?Utf-8?B?RVM=?= Microsoft Access 4 25th Jan 2007 09:01 PM
How to make Access stop adding records to my tables when I switch from Form view to Design view Mister John Doe Microsoft Access Forms 4 4th Jan 2005 04:31 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 07:49 AM.