PDA

Click to See Complete Forum and Search --> : Access 2000


honeybee
Jul 15th, 2000, 03:26 AM
VB 6.0 doesn't work with Access 2000. I have tried this combination through DAO and VisData. This is also clear from the no. of problems posted on this forum for Access 2000. Any comments?

Harrild
Jul 15th, 2000, 04:01 AM
As far as i know VB 6.0 was create for maximum functionality with Access 2000.

Did you try ADO?
(using an adodc for example?)

I never heard of this before...god i need sleep. i'm knackered - the only this keeping me awake is listening to Monty Python and the want of the food.

honeybee
Jul 15th, 2000, 04:10 AM
I have not tried using ADO. Maybe it works. But the idea behind VB-MS Access combination was to provide a default back end database support for VB applications. If you cannot use Access 2000 with DAO or VisData, you might as well discard these features from VB 6.0 Also since Office 2000 was released after Visual Studio 6.0, I am doubtful whether VB 6.0 was intended to work best with Access 2000.

Clunietp
Jul 15th, 2000, 11:19 AM
http://support.microsoft.com/support/kb/articles/q238/4/01.asp?LNG=ENG&SA=ALLKB

honeybee
Jul 24th, 2000, 12:50 AM
Many many thanks, Clunietp!

I just visited the URL you mentioned. I am yet to try it out, but I think it will solve my problem.

Edneeis
Jul 25th, 2000, 11:15 PM
Yes you should use an ADO connection and also Access 2000 uses the Jet 4.01 engine instead of the 3.51 so if you are still using the MS Jet 3.51 drivers then that is why it wont work, try switching to 4.01.

Kurian
Jul 26th, 2000, 09:43 PM
Well you could also just download Service pack 4, just go to msdn.microsoft.com and do a search on visual studio and sp4

Harrild
Jul 27th, 2000, 01:54 AM
i've just had it confired VB6.0 can only use ADO to access ACCESS 2000 DB's. DAO is now out dated by ADO. oh and while i'm on the subject. ADO can can be used to access Borland's db engine. Heeps good.

Just thought i'd let you know.

:):):):):):):):):)
------------------
:):):):):):):):):)

honeybee
Jul 27th, 2000, 02:36 AM
Thanks all you guys. You have provided a very useful info to me.

Kurian
Jul 27th, 2000, 01:16 PM
I believe with Service pack 4 you can connect to access 2000 with dao.. Though dunno why you would really want to :) (Not a big dao fan)

JHausmann
Jul 27th, 2000, 01:54 PM
Originally posted by Kurian
I believe with Service pack 4 you can connect to access 2000 with dao.. Though dunno why you would really want to :) (Not a big dao fan)

It would allow you to use Access 2000 without having to re-write existing VB code that uses DAO. It's a way of making sure Microsoft sells as many copies of Access2000 as they can...

eureka
Aug 13th, 2000, 09:09 AM
When I moved to Access 2000 I had already installed Service Pack 4. I am using VB6. The following comments are from my code and relate to the changes you have to make to use Access 2000.

'Access 2000
'For ADO (or the ADO Data Control), use the "Microsoft.Jet.OLEDB.4.0" provider.

'For DAO, go to Project menu, and choose References to use the "Microsoft DAO 3.6 Object Library."
' which must be above ActiveX Data Objects 2.1 Library or 'will trigger an error

'If you use the generic Data-Control, you need to open a DAO 3.6 recordset and then assign it to be the source of the Data Control as follows:

'Code for Form
'Private db As Database
'Private rs As DAO.Recordset
'Dim sPath As String'

'sPath = "C:\Program Files\Microsoft Office\Office\Samples\Northwind.mdb"
'Set db = DBEngine(0).OpenDatabase(sPath)
'Set rs = db.OpenRecordset("Customers")
'Set Data1.Recordset = rs
'End of Access 2000

parksie
Aug 13th, 2000, 09:33 AM
To use DAO, you need version 3.6 or above. PS: Personal opinions, I prefer DAO to ADO.

JohannS
Aug 22nd, 2001, 03:13 AM
Hi There

I've managed to get my app connected to Access 2k with Adodc, but I want to use Visual Data Manager as well, and that doesn't seem to work at all!

Any help?

BoomerK
Aug 22nd, 2001, 04:00 PM
Originally posted by JohannS
Hi There

I've managed to get my app connected to Access 2k with Adodc, but I want to use Visual Data Manager as well, and that doesn't seem to work at all!

Any help?

You may need to modify the Visual Data Manager source code and recompile it. This MSDN Howto tells you how to make the changes to the visdata project. It's surprisingly easy.

HOWTO: Modify the Visual Data Manager (VISDATA) to Work with Access 2000 Databases (http://support.microsoft.com/support/kb/articles/Q252/4/38.ASP)

Beacon
Aug 22nd, 2001, 07:41 PM
And dont go get sp4 get the latest sp5!
But it's a biggun so only do it if need be!

honeybee
Aug 23rd, 2001, 01:00 PM
Originally posted by Beacon
And dont go get sp4 get the latest sp5!
But it's a biggun so only do it if need be!

I would doubt it. Just the other day, I installed VB6 and then SP5 in my office PC and two of the Microsoft ActiveX controls just disappeared. They are the masked edit control and the mscomm control. They sure do get installed with VB6, but SP5 installation removed them somehow. Then I reinstalled VB6 with SP4.

.

Beacon
Aug 24th, 2001, 12:51 AM
Sp5 has been known to do that!
Weird i know!

But i always make up backup b4 updating!!

JohannS
Sep 27th, 2001, 05:11 AM
The Visual Data Manager, although able to connect to Access 2k DB's, became painfully slow after the 'conversion'.

Just a thought.