Access 2007 inconsistant error
in [Reports]
|
From: vtj on 1 Jul 2008 16:39 I am running a report that will run about 50% of the time. When it doesn't run, I get the "Microsoft Office Access has encountered a problem and needs to close" message. If I save the file as a 2003 .mdb it will run all the time. Is there anything in the 2007 .accdb version that will cause the intermittant error? Has anyone else run into this problem? TIA
From: Allen Browne on 2 Jul 2008 00:14 Start by running a standard recovery sequence: http://allenbrowne.com/recover.html Those steps address several possible causes of corruption. It's generally quicker to run through them than to try to pin down which one might be causing your issue. -- 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. "vtj" <vtj(a)discussions.microsoft.com> wrote in message news:697A52F3-7B37-4CE6-AA61-1FF78ECD5F6B(a)microsoft.com... >I am running a report that will run about 50% of the time. When it doesn't > run, I get the "Microsoft Office Access has encountered a problem and > needs > to close" message. If I save the file as a 2003 .mdb it will run all the > time. Is there anything in the 2007 .accdb version that will cause the > intermittant error? Has anyone else run into this problem? TIA
From: vtj on 2 Jul 2008 09:16 Thanks for your help!! Unfortunately going through the steps did not change anything. I am thinking that it is something in the way that Access processes as if the database (not compiled) were corrupt, saving it in the ..mdb format would not fix the corruption and also if corrupt it would act consistantly in 2007 format. "Allen Browne" wrote: > Start by running a standard recovery sequence: > http://allenbrowne.com/recover.html > > Those steps address several possible causes of corruption. It's generally > quicker to run through them than to try to pin down which one might be > causing your issue. > > -- > 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. > > "vtj" <vtj(a)discussions.microsoft.com> wrote in message > news:697A52F3-7B37-4CE6-AA61-1FF78ECD5F6B(a)microsoft.com... > >I am running a report that will run about 50% of the time. When it doesn't > > run, I get the "Microsoft Office Access has encountered a problem and > > needs > > to close" message. If I save the file as a 2003 .mdb it will run all the > > time. Is there anything in the 2007 .accdb version that will cause the > > intermittant error? Has anyone else run into this problem? TIA > >
From: Allen Browne on 2 Jul 2008 10:38 I have not experienced that problem. If you have not yet applied Service Pack 1 for Office 2007, that fixes heaps of issues. Get it from: http://office.microsoft.com/search/redir.aspx?AssetID=DC102486291033&Origin=HH102511011033&CTT=5 There's also a list of hotfixes here, though I don't see that any of those address the issue you describe: 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. "vtj" <vtj(a)discussions.microsoft.com> wrote in message news:2AFC7530-0145-4BA1-AD0D-5FE4DC8CA7EC(a)microsoft.com... > Thanks for your help!! Unfortunately going through the steps did not > change > anything. I am thinking that it is something in the way that Access > processes as if the database (not compiled) were corrupt, saving it in the > .mdb format would not fix the corruption and also if corrupt it would act > consistantly in 2007 format. > > "Allen Browne" wrote: > >> Start by running a standard recovery sequence: >> http://allenbrowne.com/recover.html >> >> Those steps address several possible causes of corruption. It's generally >> quicker to run through them than to try to pin down which one might be >> causing your issue.
From: vtj on 2 Jul 2008 11:09 Thank You!! I really appreciate your response. SP1 has been applied. If this problem gets resolved I'll post about it. "Allen Browne" wrote: > I have not experienced that problem. > > If you have not yet applied Service Pack 1 for Office 2007, that fixes heaps > of issues. Get it from: > http://office.microsoft.com/search/redir.aspx?AssetID=DC102486291033&Origin=HH102511011033&CTT=5 > > There's also a list of hotfixes here, though I don't see that any of those > address the issue you describe: > 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. > > "vtj" <vtj(a)discussions.microsoft.com> wrote in message > news:2AFC7530-0145-4BA1-AD0D-5FE4DC8CA7EC(a)microsoft.com... > > Thanks for your help!! Unfortunately going through the steps did not > > change > > anything. I am thinking that it is something in the way that Access > > processes as if the database (not compiled) were corrupt, saving it in the > > .mdb format would not fix the corruption and also if corrupt it would act > > consistantly in 2007 format. > > > > "Allen Browne" wrote: > > > >> Start by running a standard recovery sequence: > >> http://allenbrowne.com/recover.html > >> > >> Those steps address several possible causes of corruption. It's generally > >> quicker to run through them than to try to pin down which one might be > >> causing your issue. > >
|
Pages: 1 Prev: table/reports images Next: why is report wizard coming up with "expr1" instead of "name" etc |