PC Review


Reply
Thread Tools Rate Thread

Access 2003/ADP database corruption

 
 
alderran
Guest
Posts: n/a
 
      26th Jul 2008
Anyone else experiencing corruption problems using Access 2003 to
edit .adp files? I've been experiencing corruption problems with a
particular database. I've tried copying all the objects into a new
file, but it didn't help.

Here is an example of the problem, yesterday I added a new field to my
SQL table. To put it on the form I copied an existing text field and
converted that field from text to combo box. Quicker because I'm
using a different font/size than the Access default. Anyway each time
I did that Access would crash when I would try to save the form. When
Access would reopen the form was unusable. I couldn't even open it.
I tried it a second time just to see if it was a series of actions
that would consistently crash Access and it did crash again.


I went to a back up copy and created a new combo box field from the
toolbox and it saves fine.


That's just one of many examples. It happens all the time. If I use Access
2007 it happens less often, but still it's a pretty unstable file. I have
100's maybe even 1000's of hours devoted to it and I'm always afraid to do
anything without a million copies. Now my client is asking about making his
own changes to the forms. Which would normally be okay but not with this
file.

any help would be greatly appreciated!
 
Reply With Quote
 
 
 
 
bcap
Guest
Posts: n/a
 
      26th Jul 2008
Yep, ADP files corrupt easily and frequently.

Usually importing everything into a new file cures it, but not always!
Ensure that you make very frequent backup copies!

"alderran" <(E-Mail Removed)> wrote in message
news:2CE07C8E-2027-4348-8890-(E-Mail Removed)...
> Anyone else experiencing corruption problems using Access 2003 to
> edit .adp files? I've been experiencing corruption problems with a
> particular database. I've tried copying all the objects into a new
> file, but it didn't help.
>
> Here is an example of the problem, yesterday I added a new field to my
> SQL table. To put it on the form I copied an existing text field and
> converted that field from text to combo box. Quicker because I'm
> using a different font/size than the Access default. Anyway each time
> I did that Access would crash when I would try to save the form. When
> Access would reopen the form was unusable. I couldn't even open it.
> I tried it a second time just to see if it was a series of actions
> that would consistently crash Access and it did crash again.
>
>
> I went to a back up copy and created a new combo box field from the
> toolbox and it saves fine.
>
>
> That's just one of many examples. It happens all the time. If I use
> Access
> 2007 it happens less often, but still it's a pretty unstable file. I have
> 100's maybe even 1000's of hours devoted to it and I'm always afraid to do
> anything without a million copies. Now my client is asking about making
> his
> own changes to the forms. Which would normally be okay but not with this
> file.
>
> any help would be greatly appreciated!



 
Reply With Quote
 
Sylvain Lafontaine
Guest
Posts: n/a
 
      26th Jul 2008
And especially if you are opening your ADP project file over a bad network.

If copying or importing the objects don't work, then you should rebuild your
forms: create an empty form and then copy&paste all the controls from the
other form; after that, copy the code. To simplifying the copy of the
controls at their exact same location, add a control at the position (0,0)
before doing the copy&paste.

Also, you can change the default font/size: create a form called Normal and
then click on any control *in the toolbar*, for example the Label control.
In the property form, you should see Default Label. Change its properties
and close the Normal form. Now, all new forms will be created with the new
defaults. You can also change the default values of an existing form but
this must be done form by form. Same thing for the reports.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"bcap" <(E-Mail Removed)> wrote in message
news:488b578c$0$26080$(E-Mail Removed)...
> Yep, ADP files corrupt easily and frequently.
>
> Usually importing everything into a new file cures it, but not always!
> Ensure that you make very frequent backup copies!
>
> "alderran" <(E-Mail Removed)> wrote in message
> news:2CE07C8E-2027-4348-8890-(E-Mail Removed)...
>> Anyone else experiencing corruption problems using Access 2003 to
>> edit .adp files? I've been experiencing corruption problems with a
>> particular database. I've tried copying all the objects into a new
>> file, but it didn't help.
>>
>> Here is an example of the problem, yesterday I added a new field to my
>> SQL table. To put it on the form I copied an existing text field and
>> converted that field from text to combo box. Quicker because I'm
>> using a different font/size than the Access default. Anyway each time
>> I did that Access would crash when I would try to save the form. When
>> Access would reopen the form was unusable. I couldn't even open it.
>> I tried it a second time just to see if it was a series of actions
>> that would consistently crash Access and it did crash again.
>>
>>
>> I went to a back up copy and created a new combo box field from the
>> toolbox and it saves fine.
>>
>>
>> That's just one of many examples. It happens all the time. If I use
>> Access
>> 2007 it happens less often, but still it's a pretty unstable file. I
>> have
>> 100's maybe even 1000's of hours devoted to it and I'm always afraid to
>> do
>> anything without a million copies. Now my client is asking about making
>> his
>> own changes to the forms. Which would normally be okay but not with this
>> file.
>>
>> any help would be greatly appreciated!

>
>



 
Reply With Quote
 
a a r o n _ k e m p f
Guest
Posts: n/a
 
      28th Jul 2008
I really don't think that I've had any problems with this since Access
2000.

Honestly. Not one crash or corruption.

-Aaron


On Jul 26, 11:18*am, "Sylvain Lafontaine" <sylvain aei ca (fill the
blanks, no spam please)> wrote:
> And especially if you are opening your ADP project file over a bad network.
>
> If copying or importing the objects don't work, then you should rebuild your
> forms: create an empty form and then copy&paste all the controls from the
> other form; after that, copy the code. *To simplifying the copy of the
> controls at their exact same location, add a control at the position (0,0)
> before doing the copy&paste.
>
> Also, you can change the default font/size: create a form called Normal and
> then click on any control *in the toolbar*, for example the Label control..
> In the property form, you should see Default Label. *Change its properties
> and close the Normal form. *Now, all new forms will be created with thenew
> defaults. *You can also change the default values of an existing form but
> this must be done form by form. *Same thing for the reports.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
> "bcap" <b...@nospam.nowhere> wrote in message
>
> news:488b578c$0$26080$(E-Mail Removed)...
>
> > Yep, ADP files corrupt easily and frequently.

>
> > Usually importing everything into a new file cures it, but not always!
> > Ensure that you make very frequent backup copies!

>
> > "alderran" <alder...@discussions.microsoft.com> wrote in message
> >news:2CE07C8E-2027-4348-8890-(E-Mail Removed)...
> >> Anyone else experiencing corruption problems using Access 2003 to
> >> edit .adp files? *I've been experiencing corruption problems with a
> >> particular database. *I've tried copying all the objects into a new
> >> file, but it didn't help.

>
> >> Here is an example of the problem, yesterday I added a new field to my
> >> SQL table. *To put it on the form I copied an existing text field and
> >> converted that field from text to combo box. *Quicker because I'm
> >> using a different font/size than the Access default. *Anyway each time
> >> I did that Access would crash when I would try to save the form. *When
> >> Access would reopen the form was unusable. *I couldn't even open it.
> >> I tried it a second time just to see if it was a series of actions
> >> that would consistently crash Access and it did crash again.

>
> >> I went to a back up copy and created a new combo box field from the
> >> toolbox and it saves fine.

>
> >> That's just one of many examples. *It happens all the time. *If I use
> >> Access
> >> 2007 it happens less often, but still it's a pretty unstable file. *I
> >> have
> >> 100's maybe even 1000's of hours devoted to it and I'm always afraid to
> >> do
> >> anything without a million copies. *Now my client is asking about making
> >> his
> >> own changes to the forms. *Which would normally be okay but not withthis
> >> file.

>
> >> any help would be greatly appreciated!


 
Reply With Quote
 
alderran
Guest
Posts: n/a
 
      2nd Aug 2008
Funny thing is just yesterday I had an Access 2007 .accdb format file
crashing on me. I have a form with a subform. If I go in and set the link
master and link child properties and then hit save it crashes. I tried
copying all the objects into a new file and it still crashes.

Working with .adp files it crashes all the time too. For a while I thought
it was because I had Office 2003 and 2007 on the same pc, but recently my
hard drive died and I only installed Office 2007, yet it still crashes.

"a a r o n _ k e m p f" wrote:

> I really don't think that I've had any problems with this since Access
> 2000.
>
> Honestly. Not one crash or corruption.
>
> -Aaron
>
>
> On Jul 26, 11:18 am, "Sylvain Lafontaine" <sylvain aei ca (fill the
> blanks, no spam please)> wrote:
> > And especially if you are opening your ADP project file over a bad network.
> >
> > If copying or importing the objects don't work, then you should rebuild your
> > forms: create an empty form and then copy&paste all the controls from the
> > other form; after that, copy the code. To simplifying the copy of the
> > controls at their exact same location, add a control at the position (0,0)
> > before doing the copy&paste.
> >
> > Also, you can change the default font/size: create a form called Normal and
> > then click on any control *in the toolbar*, for example the Label control..
> > In the property form, you should see Default Label. Change its properties
> > and close the Normal form. Now, all new forms will be created with the new
> > defaults. You can also change the default values of an existing form but
> > this must be done form by form. Same thing for the reports.
> >
> > --
> > Sylvain Lafontaine, ing.
> > MVP - Technologies Virtual-PC
> > E-mail: sylvain aei ca (fill the blanks, no spam please)
> >
> > "bcap" <b...@nospam.nowhere> wrote in message
> >
> > news:488b578c$0$26080$(E-Mail Removed)...
> >
> > > Yep, ADP files corrupt easily and frequently.

> >
> > > Usually importing everything into a new file cures it, but not always!
> > > Ensure that you make very frequent backup copies!

> >
> > > "alderran" <alder...@discussions.microsoft.com> wrote in message
> > >news:2CE07C8E-2027-4348-8890-(E-Mail Removed)...
> > >> Anyone else experiencing corruption problems using Access 2003 to
> > >> edit .adp files? I've been experiencing corruption problems with a
> > >> particular database. I've tried copying all the objects into a new
> > >> file, but it didn't help.

> >
> > >> Here is an example of the problem, yesterday I added a new field to my
> > >> SQL table. To put it on the form I copied an existing text field and
> > >> converted that field from text to combo box. Quicker because I'm
> > >> using a different font/size than the Access default. Anyway each time
> > >> I did that Access would crash when I would try to save the form. When
> > >> Access would reopen the form was unusable. I couldn't even open it.
> > >> I tried it a second time just to see if it was a series of actions
> > >> that would consistently crash Access and it did crash again.

> >
> > >> I went to a back up copy and created a new combo box field from the
> > >> toolbox and it saves fine.

> >
> > >> That's just one of many examples. It happens all the time. If I use
> > >> Access
> > >> 2007 it happens less often, but still it's a pretty unstable file. I
> > >> have
> > >> 100's maybe even 1000's of hours devoted to it and I'm always afraid to
> > >> do
> > >> anything without a million copies. Now my client is asking about making
> > >> his
> > >> own changes to the forms. Which would normally be okay but not with this
> > >> file.

> >
> > >> any help would be greatly appreciated!

>
>

 
Reply With Quote
 
bcap
Guest
Posts: n/a
 
      3rd Aug 2008
The fact that Aaron has never had a crash or corruption simply proves that
he doesn't do any real work.

"alderran" <(E-Mail Removed)> wrote in message
news:FE45659B-21A4-44E1-89C8-(E-Mail Removed)...
> Funny thing is just yesterday I had an Access 2007 .accdb format file
> crashing on me. I have a form with a subform. If I go in and set the
> link
> master and link child properties and then hit save it crashes. I tried
> copying all the objects into a new file and it still crashes.
>
> Working with .adp files it crashes all the time too. For a while I
> thought
> it was because I had Office 2003 and 2007 on the same pc, but recently my
> hard drive died and I only installed Office 2007, yet it still crashes.
>
> "a a r o n _ k e m p f" wrote:
>
>> I really don't think that I've had any problems with this since Access
>> 2000.
>>
>> Honestly. Not one crash or corruption.
>>
>> -Aaron
>>
>>
>> On Jul 26, 11:18 am, "Sylvain Lafontaine" <sylvain aei ca (fill the
>> blanks, no spam please)> wrote:
>> > And especially if you are opening your ADP project file over a bad
>> > network.
>> >
>> > If copying or importing the objects don't work, then you should rebuild
>> > your
>> > forms: create an empty form and then copy&paste all the controls from
>> > the
>> > other form; after that, copy the code. To simplifying the copy of the
>> > controls at their exact same location, add a control at the position
>> > (0,0)
>> > before doing the copy&paste.
>> >
>> > Also, you can change the default font/size: create a form called Normal
>> > and
>> > then click on any control *in the toolbar*, for example the Label
>> > control..
>> > In the property form, you should see Default Label. Change its
>> > properties
>> > and close the Normal form. Now, all new forms will be created with the
>> > new
>> > defaults. You can also change the default values of an existing form
>> > but
>> > this must be done form by form. Same thing for the reports.
>> >
>> > --
>> > Sylvain Lafontaine, ing.
>> > MVP - Technologies Virtual-PC
>> > E-mail: sylvain aei ca (fill the blanks, no spam please)
>> >
>> > "bcap" <b...@nospam.nowhere> wrote in message
>> >
>> > news:488b578c$0$26080$(E-Mail Removed)...
>> >
>> > > Yep, ADP files corrupt easily and frequently.
>> >
>> > > Usually importing everything into a new file cures it, but not
>> > > always!
>> > > Ensure that you make very frequent backup copies!
>> >
>> > > "alderran" <alder...@discussions.microsoft.com> wrote in message
>> > >news:2CE07C8E-2027-4348-8890-(E-Mail Removed)...
>> > >> Anyone else experiencing corruption problems using Access 2003 to
>> > >> edit .adp files? I've been experiencing corruption problems with a
>> > >> particular database. I've tried copying all the objects into a new
>> > >> file, but it didn't help.
>> >
>> > >> Here is an example of the problem, yesterday I added a new field to
>> > >> my
>> > >> SQL table. To put it on the form I copied an existing text field
>> > >> and
>> > >> converted that field from text to combo box. Quicker because I'm
>> > >> using a different font/size than the Access default. Anyway each
>> > >> time
>> > >> I did that Access would crash when I would try to save the form.
>> > >> When
>> > >> Access would reopen the form was unusable. I couldn't even open it.
>> > >> I tried it a second time just to see if it was a series of actions
>> > >> that would consistently crash Access and it did crash again.
>> >
>> > >> I went to a back up copy and created a new combo box field from the
>> > >> toolbox and it saves fine.
>> >
>> > >> That's just one of many examples. It happens all the time. If I
>> > >> use
>> > >> Access
>> > >> 2007 it happens less often, but still it's a pretty unstable file.
>> > >> I
>> > >> have
>> > >> 100's maybe even 1000's of hours devoted to it and I'm always afraid
>> > >> to
>> > >> do
>> > >> anything without a million copies. Now my client is asking about
>> > >> making
>> > >> his
>> > >> own changes to the forms. Which would normally be okay but not with
>> > >> this
>> > >> file.
>> >
>> > >> any help would be greatly appreciated!

>>
>>



 
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: Access 2003 Terminates Unexpectedly (Database Corruption) Tony Toews [MVP] Microsoft Access 0 6th Aug 2009 12:15 AM
Re: Access 2003 Terminates Unexpectedly (Database Corruption) John Spencer Microsoft Access 0 4th Aug 2009 06:45 PM
Access Database without any corruption ? pacala_ba Microsoft Access 0 16th Nov 2008 01:14 PM
Access database corruption =?Utf-8?B?TWlrZU5hcA==?= Microsoft Access 9 14th May 2008 02:58 AM
Access Database Corruption =?Utf-8?B?QmVuVw==?= Microsoft Access 3 25th Mar 2004 06:37 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 06:19 PM.