PageSetup properties keep changing
in [Reports]
|
Prev: easiest way to create gridlines in an Access 2003 report
Next: stLinkcriteria no longer working (since 2007 upgrade)
From: PayeDoc on 7 Jun 2010 09:41 Hello All I recently had some mdb corruption problems, that I THINK I've solved - by creating a new mdb and importing all objects. A new problem has now started that is either coincidental or is somehow related to my having done the mdb rebuild. The page setup properties of various reports changes, periodically, 'by iteslf'! I have been able to repeat this behaviour to some extent: 1. preview report - discover that the page setup properties are completely wrong 2. close the report 3. select the report in the main database window, go File>Page Setup, correct the properties 4. preview report - the page setup properties are now ok 5. close the report 6. amend a parameter on the open form that is used by the report 7. preview report - discover that the page setup properties are completely wrong again! This doesn't always happen, and I have been unable to identify any pattern. The page setup properties are the margins, the landscape/portrait setting, and in one case the printer - changed from 'specified printer (correct) to default printer (not corect). I had been advised that setting the page setup properties from the File menu item in the main database window was more reliable than setting them from the report's design view - hence step 3 above. Can anyone shed any light on this? Thanks for any help. Leslie Isaacs
From: Allen Browne on 7 Jun 2010 10:22 Make sure Name AutoCorrect is turned off. Then compact the database. Explanation: http://allenbrowne.com/bug-03.html If this is Access 2007, make sure you have applied the service packs. SP2 is here: http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en -- 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. "PayeDoc" <enquiries(a)gppayroll.org.uk> wrote in message news:OqxC#akBLHA.3880(a)TK2MSFTNGP04.phx.gbl... > Hello All > > I recently had some mdb corruption problems, that I THINK I've solved - by > creating a new mdb and importing all objects. A new problem has now > started > that is either coincidental or is somehow related to my having done the > mdb > rebuild. > > The page setup properties of various reports changes, periodically, 'by > iteslf'! I have been able to repeat this behaviour to some extent: > > 1. preview report - discover that the page setup properties are completely > wrong > 2. close the report > 3. select the report in the main database window, go File>Page Setup, > correct the properties > 4. preview report - the page setup properties are now ok > 5. close the report > 6. amend a parameter on the open form that is used by the report > 7. preview report - discover that the page setup properties are completely > wrong again! > > This doesn't always happen, and I have been unable to identify any > pattern. > The page setup properties are the margins, the landscape/portrait setting, > and in one case the printer - changed from 'specified printer (correct) to > default printer (not corect). I had been advised that setting the page > setup > properties from the File menu item in the main database window was more > reliable than setting them from the report's design view - hence step 3 > above. > > Can anyone shed any light on this? > > Thanks for any help. > Leslie Isaacs > >
From: PayeDoc on 7 Jun 2010 10:57
Hello Allen Very many thanks for your response to this. I am using Access 2000, and I have found that the Name AutoCorrect was turned on: it's now off! I note from your reference that you suggest creating a new mdb, turning off Name AutoCorrect, then inporting all objects. Is that really going to be better than just turning the feature off then doing a compact/repair? Thanks again Les "Allen Browne" <AllenBrowne(a)SeeSig.Invalid> wrote in message news:O76eNzkBLHA.5584(a)TK2MSFTNGP06.phx.gbl... > Make sure Name AutoCorrect is turned off. > Then compact the database. > Explanation: > http://allenbrowne.com/bug-03.html > > If this is Access 2007, make sure you have applied the service packs. SP2 is > here: > http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en > > -- > 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. > > > "PayeDoc" <enquiries(a)gppayroll.org.uk> wrote in message > news:OqxC#akBLHA.3880(a)TK2MSFTNGP04.phx.gbl... > > Hello All > > > > I recently had some mdb corruption problems, that I THINK I've solved - by > > creating a new mdb and importing all objects. A new problem has now > > started > > that is either coincidental or is somehow related to my having done the > > mdb > > rebuild. > > > > The page setup properties of various reports changes, periodically, 'by > > iteslf'! I have been able to repeat this behaviour to some extent: > > > > 1. preview report - discover that the page setup properties are completely > > wrong > > 2. close the report > > 3. select the report in the main database window, go File>Page Setup, > > correct the properties > > 4. preview report - the page setup properties are now ok > > 5. close the report > > 6. amend a parameter on the open form that is used by the report > > 7. preview report - discover that the page setup properties are completely > > wrong again! > > > > This doesn't always happen, and I have been unable to identify any > > pattern. > > The page setup properties are the margins, the landscape/portrait setting, > > and in one case the printer - changed from 'specified printer (correct) to > > default printer (not corect). I had been advised that setting the page > > setup > > properties from the File menu item in the main database window was more > > reliable than setting them from the report's design view - hence step 3 > > above. > > > > Can anyone shed any light on this? > > > > Thanks for any help. > > Leslie Isaacs > > > > |