Dear List,
I have been given the task to make a small data entrytool on MS access 2000.
THis tool must do the following.
- provide 6 forms for entering data Memo, Text Date etc.
- write binary files, to the OLE Object database field, from the filesystem,
which could be any format in theory.
- There is about 11 tables with some 1:N relationships.
I already have had alot of experience with using ADO from VB, so I guess it
would be easier for me to use ADO (in comparison with DAO). But to me it
seems messy somehow to start making ADO connections within modules, and it
would be better to use native access objects as created by the Access
wizards. I have already got some code to write the blobs to the database
without ado.
What do the access profis think I should do. is it bad to somehow have ADO
code like below inside access, and keep it open the whole time?
Set Conn = New ADODB.Connection
With Conn
.CommandTimeout = 50
Debug.Print Access.CurrentDb.Name
.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data source="
& Access.CurrentDb.Name & _
";Mode=Share Deny None"
.Open
End With
In addition, to what extent can the ADO recordset objects be used together
with the Access objects available (like Form). I would really appreciate any
pointers.
regards
Ben
|
Similar Threads
