If only i had the time to combine this with http://www.databasejournal.com/features/msaccess/article.php/3848121/Extending-the-InputBox-function-for-MS-Access-Forms.htm

Spare time? Anybody?

Tnx 4 your beautiful messagebox. I only have one question: is it possible to use a vbTab in the message?

With regards, Marianne

First few lines of Form_FormDialog::ShowModal are: If m_Title <> “” Then caption = m_Title & ” ” Else caption = CurrentDb.Properties(“AppTitle”) End If

Thanks again, Matthew Pfluger

Next issue please, I like to set the mouse pointer to jump to default buttons on dialog boxes which works with the standard Access 2007 dialogs but not with my new good looking ones. Is it possible to obtain this behaviour on the custom dialog box? Regards John

My main issue is that I don’t have any older version of Access so I can’t really test the implementation and be sure about the result. Just saving the project in an older format won’t work properly at I’m using some A2007-specific features.

Thanks Tom

older versions don’t have rich-edit textboxes, so you would probably have to rely on a webbrowser component and that would change a lot.

If you are OK with being limited to the plain version of the enhanced MsgBox, then your only other issue should be with displaying transparent images for the icons.

To Henry: yes please, send the fix and I will update the code and the samples for everyone. My email is in the footer of the page. Thank you.

I have the Enhanced MsgBox getting called during an “on click” event on a button by using =RichBox([field]).

Any ideas?

I’ll make a note of your suggestion for the next update and probably add it as an option (or a default that can be disabled).

Cheers from downunder Scott

@Renaud: brilliant work!

Now there’s a variation I would love to see: A modified InputBox! Could you do that, too?

Regards from Germany,

Stefan

There’s one extension I’d like to implement or see implemented, autowrap for long texts.

There’s one slight problem with the code as it stands… The Default Buttons are not set properly. The Code for this looks fine until you notice that the buttons are named in the reverse order to their use. bt3 is used as button1, etcetera. The rest of the code reflects this, the Timer event which sets the default does not. Easy to change in the timer event just replace each occurence of bt1 with bt3 and bt3 with bt1.

Thanks again, Andycr

A friend sent me the A2003 version, but it now appears that the RichText.ocx is blocked because of security reasons (apparently they deem it safe in A2007). I registered RICHTX32.ocx 6.0 (SP6) under references, but the 2003 mdb doesn’t compile: ‘acTextFormatHTMLRichText’ is not found -- I found a registry-patch here: http://p2p.wrox.com/topic.asp?TOPIC_ID=10894 -- doesn’t work on my pc.

There is also a replacement, by Stephan Lebans: http://www.lebans.com/richtext.htm -- registering it, didn’t help either.

Also, the .png images don’t load -- apparently they don’t get included on converting -- could you include them separately?

Any suggestions? I really would like to give this replacement a try -- I do see its potential, but as I don’t have A2007, I can’t run it as such.

Would like to suggest an enhancement….ability to specify customer text for two. I often have a business case where I am displaying a message box asking the user if they want to replace or open the existing.

@Larry: still not sure why you’re getting this. Could you send me a zip file of your application so I can investigate? Send it to accessblog#nkadesign* (replacing # by @ and * by .com).

Out of Stack Space Error

Occurs when modifying DefaultButtonDelay Try modifying the Enable Buttons In: field in sample form

Problem occurs in module “Dialog”

Reads:

Public Property Let DefaultButtonDelay(delay As Long)
    If delay < 0 Then delay = 0
    DefaultButtonDelay = delay
End Property

Should read:

Public Property Let DefaultButtonDelay(delay As Long)
    If delay < 0 Then delay = 0
    m_DefaultButtonDelay = delay
End Property

@Alan: it’s a good point and it could make replacement much easier, although I usually prefer to err on the side of caution and avoid overriding base functionality to avoid unintended consequences (and keep in line with the “element of least surprise” motto by making things explicit). :-)

I gave it a shot and without the RTF it just wouldn’t be the same; so I chose not to pursue it any further.

The Access 2007 version is striking! Thanks!

Moo

You can do without the module by manipulating the class module’s Instancing property. The catch is that the property sheet doesn’t allow the setting you need but you can run a single statement in the immediate window to do the job. See this post http://www.utteraccess.com/forums/showthreaded.php?Cat=&Number=1441683&page=&view=&sb=5&o=&vc=1

Glenn

@Moo: please be my guest. I have been thinking about this recently but since I only have Access 2007 testing for older version is a bit of a challenge.

Adapting the code to older versions should not be difficult if you stick to plain text. You will have to remove references to the “TextFormat” property of the txtMessage textbox as it is new in Access2007 and used to switch between plain text and rich text.

As far as I know, the only way to bring rich text to older versions of Access is to use a webbrowser control.

If you manage to convert it, please send me the updated database so I can host it here for all to find.

Thanks for that. Your explanation makes perfect sense and I can’t think of a compelling reason to suggest that a class based alternative would be preferable. Code libraries are certainly the way to go for frequently used code.

While using a class in this case doesn’t appear to offer an advantage over your standard module approach, you might be interested to know that there are a couple of ways to include classes in code libraries such that any application using the library can create instances of the relevant classes.

Glenn

It doesn’t mean it can’t be done. I just don’t think it bring anything useful doing it in a Class as opposed to a Module in this case.

Maybe I’m wrong and there is a better way.

In that case let me know :-)

I have briefly looked over your custom message box concept and like what I see. I am curious, however, because unless I am mistaken you have implemented it in Access using standard modules rather than as a class. Is there any particular reason you didn’t create a class instead?

Glenn

Your website was a real find. I love the enhanced message box utility for Access, as well as the modal dialogs with transparent backgrounds. These are awesome tools that help Access developers to create interfaces that have some visual appeal. Thanks so much for your efforts and generosity.

Ken Warthen

i cannot say more . . . this is extremely good . . .

i saw other solutions but yours surpass all others, congratulations . . .

keep on doing the good work . . .