Results 1 to 3 of 3

Thread: VB6 Intrinsic Data Control & Access 2000

  1. #1

    Thread Starter
    New Member
    Join Date
    Aug 1999
    Posts
    1

    Post

    Is there a fix yet to using the IDC of VB6 with DAO 3.6 during design time with an Access 2000 database?

    Using Data Environment, what control will show pictures (BMP) stored in Access 2000 data base?

    Thanks

  2. #2
    Member
    Join Date
    Apr 1999
    Location
    Kirkland, WA, USA
    Posts
    40

    Post

    I would answer the datacontrol question with a bit of history ... shortly after VB3 came out with its new "intrinsic database" Jet version 1.1, Access moved up to Jet 2. After some time we got a "connectivity level" so that we could work with Jet2 and this connectivity continued with the release of VB4 ... then Access 95 (5) came out with Jet3 and once again VB could not speak with Access-created databases.

    With VB5 we got a time-out on this out-of-synch pattern since Jet did not have any major structure changes and up thru Access 97 both products we in the Jet3x window.

    So you see, with the release of Access 2000 comes Jet4 and the problems you are experiencing are seen by old timers as StandardOperatingProcedure for VB/Access releases. The danger from us old folks however is to think that all will be resolved like in the .

    There is a darker side this time around

    Because of ADO, this time around there is a good chance that VB wil not get an upgraded DAO datacontrol at all. Here's a unique problem: Not all programmers can afford to deply ADO apps. PLUS: Even MS states (see June 1999 VBPJ and the Office2000 VB developer's Guide) that DAO is the better choice for Jet/ISAM development. However, while they are stating this openly they are not talking about updating the DAO data control.

    This logic is flawed, right? MS says to keep using DAO yet seems to not be considering supporting it (with new data controls). IMHO, their logic made sence *until they admitted in print* that DAO was the better choice for a lot of Jet/ISAM development.

    And here is the best way to let them know that we are aware of the logic problem and that we would appreciate their addressing it:

    write a professional note to [email protected]

    letting them know that you have seen their notes about DAO being advised for a number of Jet/ISAM projects and firmly, but prfessionaly, urge them to address their own new advice by releasing at least one last DAO datacontrol to handle Jet4.

    If they don't hear from you then they will not see any problem. They are good people but just people and the squeaky wheels get taken care of if they squeak enough.

    -Smith

    ------------------
    http://www.smithvoice.com/vbfun.htm

  3. #3
    Member
    Join Date
    Apr 1999
    Location
    Kirkland, WA, USA
    Posts
    40

    Post

    As to the use of graphics (or avis or quicktimes or wavs any binaries) in a database, if you want to do it simply and with no training wheels (<g> ) then look at the step by step at:
    http://www.smithvoice.com/appendin.htm

    the demo shows more than just getting/putting it also has a nice ratio-related way of printing thumbnails. It is DAO but ADO is the same deal (the WROX PRess book ADO2.0 Programmer's Guide www.wrox.com) shows ADO chunking if you have any problems seeing the ADO in DAO

    Hope it helps!
    -Smith

    ------------------
    http://www.smithvoice.com/vbfun.htm

Posting Permissions

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



Click Here to Expand Forum to Full Width