Visual Basic&database, using access databases by using ODBC

using access databases by using ODBC

Author	Message
Cem Ozudemirtur #1 / 9	using access databases by using ODBC hi everyone... I just need some help on my project..i hope someone can help... what my problem is I want to reach to Access database from data control by using ODBC...I had a few tries but was unsuccessful...they were ended with the message telling me: "you can not use ODBC to import from, expert to or link an external MS Access or ISAM database table to your database!" I need urgent help...if anyone knows what is wrong here?and also how we can do this then please give a hand. looking forward for your reply. thanks in advance! cem
Mon, 16 Aug 1999 03:00:00 GMT

Mark T Crawfor #2 / 9	using access databases by using ODBC Why do you need to use ODBC? .. Mark Quote: > hi everyone... > I just need some help on my project..i hope someone can help... > what my problem is I want to reach to Access database from data control > by using ODBC...I had a few tries but was unsuccessful...they were ended > with the message telling me: > "you can not use ODBC to import from, expert to or link an external MS > Access or ISAM database table to your database!" > I need urgent help...if anyone knows what is wrong here?and also how we > can do this then please give a hand. > looking forward for your reply. > thanks in advance! > cem
Mon, 16 Aug 1999 03:00:00 GMT

William Harr #3 / 9	using access databases by using ODBC says... Quote: >Why do you need to use ODBC? >.. Mark >> hi everyone... >> I just need some help on my project..i hope someone can help... >> what my problem is I want to reach to Access database from data control I can't speak for Cem, but an ODBC trace can be very revealing when trying to decipher what Visual Basic and the Jet engine are doing behind the scenes. I've also had reason to wish to be able to use an Access ODBC driver, just to provide a baseline with respect to other ODBC drivers. ODBC drivers are a lot better nowdays than they used to be, but if there is a problem with an ODBC driver, you make a much better case for choosing one driver over another, or for complaining to the vendor, if you can better tell what is going wrong. --
Tue, 17 Aug 1999 03:00:00 GMT

Mark T Crawfor #4 / 9	using access databases by using ODBC Quote: > says... > >Why do you need to use ODBC? > >.. Mark > >> hi everyone... > >> I just need some help on my project..i hope someone can help... > >> what my problem is I want to reach to Access database from data control > I can't speak for Cem, but an ODBC trace can be very revealing when trying > to decipher what Visual Basic and the Jet engine are doing behind the scenes. > I've also had reason to wish to be able to use an Access ODBC driver, just to > provide a baseline with respect to other ODBC drivers. ODBC drivers are a lot > better nowdays than they used to be, but if there is a problem with an ODBC > driver, you make a much better case for choosing one driver over another, or > for complaining to the vendor, if you can better tell what is going wrong. > -- William, I absolutely agree with you here, ODBC traces are revealing. I have a tendency to overlook ODBC drivers if a "native" interface exists (an obvious failing on my part). I will definitely keep a more open mind in the future. Thanks for the reminder.. Mark
Tue, 17 Aug 1999 03:00:00 GMT

Eric M. Wood #5 / 9	using access databases by using ODBC Quote: > hi everyone... > I just need some help on my project..i hope someone can help... > what my problem is I want to reach to Access database from data control > by using ODBC...I had a few tries but was unsuccessful...they were ended > with the message telling me: > "you can not use ODBC to import from, expert to or link an external MS > Access or ISAM database table to your database!" > I need urgent help...if anyone knows what is wrong here?and also how we > can do this then please give a hand. > looking forward for your reply. > thanks in advance! > cem Nobody has answered this guys question. The reason you are getting an error is because The Access database you are trying to get to is not an ODBC record source, also, it does not need to be. In the DatabaseName property of te data control enter the full Path to the Access file, the RecordSource property of the data control should be the name of the table or query in your database good luck
Tue, 17 Aug 1999 03:00:00 GMT

mitc #6 / 9	using access databases by using ODBC I don't know why you're using ODBC, but I can only assume its for future migration to a different backend. A good, although not optimal, solution if this is your scenario is to encapsulate your data access in well designed classes( or functions that return recordsets) using DAO. Then in the future, just modify the data access functions without touching the rest of your code. Has worked for me many times. Stuart Mitchell Owner and CEO Aquarius Itech Brisbane Australia Quote: > what my problem is I want to reach to Access database from data control > by using ODBC...I had a few tries but was unsuccessful...they were ended > with the message telling me: > "you can not use ODBC to import from, expert to or link an external MS > Access or ISAM database table to your database!"
Wed, 18 Aug 1999 03:00:00 GMT

William Harr #7 / 9	using access databases by using ODBC Quote: >Nobody has answered this guys question. The reason you are getting an >error is because The Access database you are trying to get to is not an >ODBC record source, also, it does not need to be. In the DatabaseName The original request was to get access to an Access database via ODBC, not via the built-in drivers (whatever they are). I agree, with Visual Basic, you don't need an ODBC driver. I have presented a couple of reasons why you might want to use ODBC, rather than the built-in driver. Personally, I am quite annoyed that Visual Basic doesn't give me that option. If ODBC (a Microsoft-led standard) is good, then why does Microsoft with VB 4 not let me use an Access ODBC driver? - William Harris
Wed, 18 Aug 1999 03:00:00 GMT

Jim Gilber #8 / 9	using access databases by using ODBC Quote: > >Nobody has answered this guys question. The reason you are getting an > >error is because The Access database you are trying to get to is not an > >ODBC record source, also, it does not need to be. In the DatabaseName <snip> For whatever reason, in their infinite wisdom MS has made the Access MDB database format available via ODBC ONLY if you use the ODBC API, not through normal DAO syntax. -- Jim Gilbert Junk added to EMail address to thwart auto-mailers All opinions my own, blah blah blah. (Insert your favorite disclaimer here).
Thu, 19 Aug 1999 03:00:00 GMT

Jim Forsyth #9 / 9	using access databases by using ODBC Quote: > I don't know why you're using ODBC, but I can only assume its for future > migration to a different backend. > A good, although not optimal, solution if this is your scenario is to > encapsulate your data access in well designed classes( or functions that > return recordsets) using DAO. Then in the future, just modify the data > access functions without touching the rest of your code. Has worked for me > many times. > Stuart Mitchell > Owner and CEO > Aquarius Itech > Brisbane Australia > > what my problem is I want to reach to Access database from data control > > by using ODBC...I had a few tries but was unsuccessful...they were ended > > with the message telling me: > > "you can not use ODBC to import from, expert to or link an external MS > > Access or ISAM database table to your database!" The other method that I have used is to use linked ODBC tables in the mdb file, and just use DAO when accessing these table names. Then you can also have a parallel set of tables that are native access, and use a renaming procedure to rename the tables from native access to the linked tables, or vice versa. While DAO is not the optimal method for access to ODBC, this does give you the flexibility to go between straight Access tables or ODBC linked tables with just a rename of the tables in the MDB file. This also works for any querydefs defined against these table names. The querydefs can remain the same because all they care about are the table names. -- ___________________________________________________________ phone - 513-576-2629 fax - 513-576-2843 "Preach the gospel at all times - if necessary, use words." St. Francis
Sun, 22 Aug 1999 03:00:00 GMT

Page 1 of 1

[ 9 post ]