Page 1 of 2 12 LastLast
Results 1 to 15 of 25
  1. #1
    n2cheval
    Guest

    Access 2000 Runtime or VB 6 (Access 2000 Developer)

    I'm not sure this is the right place to ask this question, yet apparently there is a lot of things I don't know.
    I've developed a prototype database application with modem communications for a client on their machine in Access 97. They seem happy with the design, logic and workings (speed) and now want to package it. Now I was wondering if anyone had any opinion on whether it is better to up-size it to Access 2000 and use the runtime version in the Access 2000 developer or convert it to Visual Basic 6?

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

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    How proficient are you in VB 6? If you aren't familiar with all the differences between VB forms and Access forms and comfortable with creating equivalent functionality in VB, I'd suggest going to Access 2000 instead. But what do you mean when you say they want to "package" it? In either case, you'll need the packaging and deployment wizard, even if you switch to VB. Otherwise, there is no guarantee the application will run properly on a target machine, and no license for any ActiveX controls you may have used.
    Charlotte

  3. #3
    n2cheval
    Guest

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Unfortunately, not very, I've been meaning to move there, yet so far my work has called for office, office, office. On thing though with the differences concerning VB, with each list box and combo box, would you need a separate data source for each one, as well as the form?
    Package, as in create an install that the client can run and use. The package and deployment wizard is fine for both VB and Access 2000 as I have the developer version.
    No license for the ActiveX controls in Access or VB? I believed the VB ones were licensed and in Access only using one extra which says no royalties needed.

  4. #4
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    I'm not sure I understand what you mean by "up-sizing it to Access2000", other than the Access2000 runtime takes 80MB+ whereas the Access97 runtime is only about 10MB.

    It would probably be easier to deploy a VB application. However, how long will it take you to redo it in VB? While there are many similarities, there are some big differences; does VB allow you yet to use subforms like Access does? You could conceivably have the Access2000 version ready to go tomorrow.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  5. #5
    n2cheval
    Guest

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Upsizing: Converting the Access 97 database to an Access 2000 database.

    redo in VB? That's what I don't know. I don't have much experience in VB except from maintenance point of view. From the looks of it likely a fair amount of time. Yes from what you said, VB does not do Subforms the same way as Access. So I would have to find another solution. I have one, yet it is not as easy to implement.

    Doing the Access 2000 version is the way I am thinking, yet I wanted some other opinions before I suggest it to the client as an option.

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

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Unless you're a good VB programmer, stick with Access. You need a bunch of ActiveX controls to (I'm including the ADO DataControl and the related combo and listbox controls in that group) to even begin to get the funtionality you have built into Access forms. VB 6 reports are closer than its forms to the Access equivalent, but they lack the flexibility and richness of Access reports. The learning curve to convert is fairly steep, even if you use a product like AccessToVB, which will still force you to go in and manually edit the code and the objects to make them work.
    Charlotte

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

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Royalties have nothing to do with the licensing issue. The activeX controls that come with Office 2000 developer edition are redistributable because the developer edition gives you the license for them, but the activeX controls that come with VB 6 are only redistributable if you have the Professional version or higher. Unfortunately, just about everything you might want to do in VB to emulate the Access environment is going to require ActiveX controls.
    Charlotte

  8. #8
    n2cheval
    Guest

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Well I've got VB 6 Professional and Crystal Reports Developer to use. So it's a learning curve with both. Yet I can use Crystal with Access 2000 I think.

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

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Why bother to use Crystal Reports if you're using Access 2000? The Access report generator is superior.
    Charlotte

  10. #10
    n2cheval
    Guest

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Because I didn't know how to make interactive charts and VB didn't describe much usefulness with charts either.

    It is only today that I considered an Access 2000 runtime approach, for the last week it has been only VB app.

  11. #11
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    I guess I wouldn't call converting from Access97 to Access2000 "upsizing". To me, "upsizing" would be converting to SQL Server.

    Who are your customers? That is, who are you packaging this for? Is it remote users of your client company, or is it just anyone? Obviously, Access 2000 is the cheapest way to go from your standpoint. Just make sure you have ironed out all the potential problems with using the runtime (I don't know how familiar you are with it). Things that are easy to do from a full Access version can't be done from runtime; like invoking the Linked Table Manager, or even printing from print preview mode!
    Then, there is always the missing references problem that might rear it's ugly head.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  12. #12
    4 Star Lounger
    Join Date
    Jan 2001
    Location
    Altnau, Thurgau, Switzerland
    Posts
    447
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    If it exists as an Access 97 app already, then why do you want to convert to Access 2000 for distribution? Why not distribute as Access 97.
    An Access 2000 runtime installation can take up to 150 MB on the target machine depending on its current configuration and make numerous changes.
    An Access 97 runtime would very likely be less than 20 MB and perform fewer changes to the target machine.

  13. #13
    4 Star Lounger
    Join Date
    Jan 2001
    Location
    Altnau, Thurgau, Switzerland
    Posts
    447
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Charlotte have you used Crystal reports?
    I use both Access and Crystal. Access report generator is easier to use. However I believe the possibilites available in crystal make it a much better report generator at the end.

  14. #14
    n2cheval
    Guest

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    Remote users to the client company. I've looked up the doco on Access 2000 runtime on the MS website so I'm with you there. Yes and missing references can always be a problem. <img src=/S/smile.gif border=0 alt=smile width=15 height=15>

    Thanks for your reply.

  15. #15
    n2cheval
    Guest

    Re: Access 2000 Runtime or VB 6 (Access 2000 Developer)

    No, my first time with crystal reports, yet I have a few friends who have and seem to know what's what with it. Yes, that is what they informed me as well concerning charting.

Page 1 of 2 12 LastLast

Posting Permissions

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