Results 1 to 3 of 3
  1. #1
    Star Lounger
    Join Date
    Dec 2000
    Posts
    70
    Thanks
    0
    Thanked 0 Times in 0 Posts

    ActiveX Control hell (97/SR-2)

    I've created an Access database which uses a Common Dialog Control in the startup switchboard form -- and everything works fine on my computer.

    However, if I put my Access database with this Common Dialog Control on anyone else's machine, it doesn't work. I get an error message saying "There Is No Object in This Control" when the startup switchboard form launches. When I look at the thing in design view, all I see is a little white box where the Common Dialog Control was.

    Just to experiment, I tried deleting and then inserting another Common Dialog Control on the problem computers -- I get another error message saying: "You don't have the license to use this ActiveX control." Huh? This is a Microsoft ActiveX control -- I need an additional license to have it work for my users?

    The only difference between myself and everyone else who I'm trying to distribute this to is that I'm running the Office 97 Developer Edition of Access and everyone else is running just regular Access 97.

    I did try looking in the Microsoft KB for a fix -- the only article I found applied to the ODE 97 version of Access. I also tried re-registering the comdlg32.ocx file on the problem machines, but that didn't help either.

    What's even more puzzling is that other Access databases with the Common Dialog Control do work on these problem computers. For example, I took an sample app from Alison Balter's CD (from her Mastering Access 97 Development book), which also has a Common Dialog Control, and it runs okay on the problem machines! (However, even though Alison's Common Dialog Control runs okay and shows up in Design View, you still get the "no license" error message if you try to insert any additional Commond Dialog Controls into her form on these problem machines.)

    Anyway, all I want is my Common Dialog Control to run okay on these problem machines. What did Alison do that I'm overlooking? For those of you who have Alison's book and CD, her file that I'm refering to is chap37.mdb.

    Thanks,

    Stephan

  2. #2
    4 Star Lounger
    Join Date
    Dec 2000
    Location
    Faifax, Virginia, USA
    Posts
    542
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: ActiveX Control hell (97/SR-2)

    i had a similar problem yesterday with AXP.
    I used the FileDialog - that crashed in A2000 (rightly so).
    I used the CommonDialog; that also crashed (not sure why).
    I wound up using dhCommonDlg from Access 2000 Developer's Handbook by Getz - Litwin - Gilbert. This worked on all machine & OSs.
    So, if you have their earlier book, I would recommend that route.

  3. #3
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: ActiveX Control hell (97/SR-2)

    Did you create a setup to install the database on the other machines? If not, then you didn't distribute the license for that control. As for Alison's example, is she using the common dialog control or calling the Windows common dialog? The latter is an API call which doesn't require a license and is my preferred method.
    Charlotte

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •