Access 2010 hide menu on startup?

[CJ_London]

I was hoping to hide it without the user having to do it themselves

and post #18

 

[RichO]

Ok that's a puzzling one because it works with the sample DB that was attached but when I copy that same code into my form it doesn't. I even imported the form and that didn't make a difference.

All I can guess is that it's because my DB is still in MDB format while the sample is ACCDB. That must be the difference and where the problem lies.

 

[CJ_London]

not something I've ever considered, using 2007+ code in a mdb in a 2007+ environment but strongly suspect you are right.

Is there any reason you cannot upgrade your mdb to an accdb?

 

[RichO]

Thinking about doing that but a little hesitant because of the errors I expect to encounter. I read about the advantages of doing so and it didn't seem like anything that I really needed.

I heard about being able to mix regular and bold text in a memo field with 2010. Is that feature only available with the new format?

 

[CJ_London]

well - this is one issue you've encountered by not changing. If you are supporting customers who still use access 2003 or earlier, then develop/maintain in 2003. If your customers are using 2007 or later then it's time for you to upgrade as well. If you are supporting both types, you need both versions.

the errors I expect to encounter

I must have updated some 40 mdb systems to accdb over the last 6 or 7 years and hit very few problems with a straight upgrade. The main issue for me is a certain element of making the forms look a bit different so it 'looks like an upgrade' and might include adding some new features such as an email function(email did not exist for my earliest systems, at least not in the way it is now), plus resisting an inclination to 'improve' the system with all the things I've learned in the succeeding years. Any straightforward system should convert OK and probably will not require any changes.

When you upgrade, a new file is created so you can always fall back on the mdb if you need to.

I heard about being able to mix regular and bold text in a memo field with 2010. Is that feature only available with the new format?

yes - plus, font size, italic, underline, color etc. But there are lots of other standard features such scaling controls to form size, more dynamic reports, etc, new controls and field types (although I tend to avoid using the latter since they are not upsizeable and in my opinion are not really for the professional developer)

It is years since I've developed in mdb but I do remember that at one time, 2003 could not access .xlsx formats - they all had to be converted to .xls before importing/linking or whatever. MS may have put a patch in for this.

ADP has disappeared and security is different so if you make use of these things you will have some work to do, but there are plenty of links out there.

I still have one client who has a mdb back end (with accdb front end). The only reason for this is replication which disappeared in 2007 and the way they are set up requires a major investment on their part to change which for now they are not prepared to finance.

 

[RichO]

I will give that a shot. Originally when I toyed around with 2010 several months back I did convert to ACCDB and I know I ran into errors with PDF creation because I am using the ReportToPDF module from A2K so every instance of that will need to be changed. I know there were a couple other issues I had.

 

[gemma-the-husky]

Rich: are you saying you used pdf creation in A2003

if you used something like Stephen Lebans method (with dynapdf.dll), then you cannot use this after A2007.

you can simply change your code with something like this

 if version>="13" then
   'use docmd.outputto acformatdpf, etc 'but see below - you need to use the actual string value, not the constant
 else
  'use Stephen lebans code (or other code to generate pdfs)
 end if

the reason these codes won't work (well Lebans, I know) is that Stephen Lebans code generated a temporary .snp snapshot file first, and then converted that to a pdf. After A2007, Access will not produce snapshots correctly, and you only get half-size pdfs.

If you use the above test, your code will build in A2003, but run in all versions. You have to be careful because trying to use the constant acformatpdf in A2003 will not work (as it doesn't exist), and instead you have to use the specific value, which I have not looked up for this note.

I still tend to build apps in A2003, which still seems to have everything I need.


as CJ says, Office 2003 did not use the xml formats and therefore does not recognize docx and xlsx formats.

 

[RichO]

Yes it was Lebans' module I was using with Access 2000. I just checked and yes, the PDF is only half there so I will need to change all of those. I won't need to make it work with both versions because we will be using 2010 for everything for this day forward.

 

[RichO]

Well, the problem with the ribbon not hiding is not an accdb vs. mdb issue either. I converted to accdb, imported the form directly from the sample DB and set it as the startup form and the ribbon does not hide. Very strange....

 

[CJ_London]

don't know how much code you have in your main form - you can always make a copy to test, but if you set the form has module property to false and save the form, it will clear the code (perhaps consider compact and repair as well). Then copy or retype the two relevant lines of code and see if that works. If it does, start copying the remaining code back.

 

[Eljefegeneo]

This is a sample of what I usually do on the first page that I want the user to see when they open the DB. My code may not be exactly right, but it does work like a charm. Please note that I have included a "Hide" and "Unhide" button on the form. I usually just make the command button so small that it looks like a tiny icon. They are a safety valve so that the form can be modified.