Microsoft Access 2010 runtime license problem

Posted on 2013-05-20
Last Modified: 2013-06-02
I have deployed the Access runtime environment for a database I have developed. It works until I get to a certain point when I get the following message:

"You do not have an appropriate license to use this functionality in the design environment"

Do I need to register something, and if so, how do I do it? Or is it something else?
Question by:rick_danger
LVL 12

Expert Comment

ID: 39182764

Author Comment

ID: 39183643
Thanks pdebaets - the trouble is that it doesn't tell me which control it is referring to. I think this error is specific to the Microsoft Access run-time program
LVL 57
ID: 39184185
<<I think this error is specific to the Microsoft Access run-time program >>

  No, there's nothing in the runtime that would do that.  once it's started, that's it.

  As peter has pointed out, you used some type of 3rd party control within the application which is from another product (like VB6 classic).

  The point at which you get the error (form or report) is what you need to look at.

   Another thing you can look at is references in VBA and check for non-native controls.


Author Comment

ID: 39184255
My Access database uses VBA, if that's what you mean. As regards non-native References, I am using:
Visual Basic for Applications
Microsoft Access 14.0 Object Library
OLE Automation
Microsoft Office 14.0 Access database engine Objects
Microst Excel 14.0 Object Library
Microst Office 14.0 Object Library
Microst Outlook 14.0 Object Library
Microsoft XML, v6.0

I think these are all native. It looks as if the code that is making it fail is in here:
Public Function SendIt(Optional email_address, Optional email_subject, Optional email_body, Optional send_email As Boolean)
    Dim OutApp As Object
    Dim OutMail As Object
'    posit = InStr(email_address, "#")
    email_len = Len(email_address)
    email_pre = Mid(email_address, 9, email_len)
    email_len = Len(email_pre)
'    email_address = Mid(email_pre, 1, email_len - 1)
    Set OutApp = CreateObject("Outlook.Application")
    Set OutMail = OutApp.CreateItem(0)
    On Error Resume Next
    SigString = Environ("appdata") & _

    If Dir(SigString) <> "" Then
        Signature = GetSig(SigString)
        Signature = ""
    End If
    With OutMail
        .To = email_address
        .CC = ""
        .BCC = ""
        .Subject = email_subject
        .HTMLBody = email_body & "<br><br>" & Signature
        Select Case send_email
        Case True
'            .Display
        Case False
'            .send
        End Select
'        .send
    End With
    On Error GoTo 0
    Set OutMail = Nothing
    Set OutApp = Nothing
End Function

Does this help?
LVL 57
ID: 39184385
That's odd...there's nothing unusual there.

Does it actually fail in this code?   What controls are on the form that invokes this code?


Author Comment

ID: 39184393
There is nothing unusual in any of the controls in the form. Mostly text boxes and buttons.
LVL 57
ID: 39184402
Can you put the form alone in a sample DB and upload?

LVL 21
ID: 39185136
On the PC generating the error with the  Access Runtime, which edition  of Microsoft Office 2010  (14) is installed?

Author Comment

ID: 39191463
HiTech - sorry for the delay, I've been away for a couple of days.
14.0.6129.5000 (32-bit)
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

LVL 57
ID: 39204426
Still would like to see a sample DB containing the form involved.


Author Comment

ID: 39204908
Not sure if this helps. Let me know
LVL 57
ID: 39205437
Well no 3rd party controls in there for sure.

Only thing odd about this form is the field references; they should not have an equals sign (=) in front of them.

If that's causing the error, that would be weird....but in any case, they don't belong there.


Author Comment

ID: 39212746
Did that, same problem...
LVL 57

Accepted Solution

Jim Dettman (Microsoft MVP/ EE MVE) earned 500 total points
ID: 39212858
Is this happening with a few users or all?

I think it's either one of two things:

1. References in the current project.

2. A problem in Outlook.

 It would be helpful if you could add some logging to that SendIt() procedure.  Better yet, download MZ Tools (Free) from here:

  Use that to add line numbers to the procedure.   Then add error handling to the procedure and include VBA.ERL as part of the error display.   This will give you the exact line # then that the error occurs on.

 That will help pin-point the error.

 Also, does Outlook start OK and work correctly on the machine(s) getting the error?  I'm also thinking a repair of Office might be in order, but let's take it one step at a time.


Author Comment

ID: 39214119
I think you have hit the nail on the head! I feel really stupid, but I've only just realised that Outlook is not installed on the target machine! In fact Office is not on it at all.

So I suppose the only way around this is to somehow install Outlook.

Thanks for your help.

Author Closing Comment

ID: 39214134
Thanks for sticking with me!
LVL 57
ID: 39214197
<<So I suppose the only way around this is to somehow install Outlook>>

 The other option is to send e-mail differently; you don't need to use Outlook.

 Outlook is simply an e-mail client and there are a number of other ways you can send e-mail if that's all your doing:

1. Use CDO -  A library of functions that all you to send and work with e-mail.

2. Use BLAT - Command line or DLL that talks directly to a SMTP server.

3. Use vbSendMail - VB class that talks directly to a SMTP server.

  An SMTP server is an e-mail server.  This is what Outlook uses to send e-mail as well.

Let me know if you want more details on anything.


Author Comment

ID: 39214291
Thanks very much for the extra help - much appreciated!

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Since upgrading to Office 2013 or higher installing the Smart Indenter addin will fail. This article will explain how to install it so it will work regardless of the Office version installed.
Using Word 2013, I was experiencing some incredible lag when typing.  Here's what worked for me....
In Microsoft Access, learn how to use Dlookup and other domain aggregate functions and one method of specifying a string value within a string. Specify the first argument, which is the expression to be returned: Specify the second argument, which …
Learn how to create and modify your own paragraph styles in Microsoft Word. This can be helpful when wanting to make consistently referenced styles throughout a document or template.

943 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

6 Experts available now in Live!

Get 1:1 Help Now