Freshman
Registered User.
- Local time
- Today, 14:20
- Joined
- May 21, 2010
- Messages
- 437
Hi all,
I still prefer to use 2003, but I need to add some functionality to an existing database which could really use the new "Attachment" data type in 2007/10.
However, that means I have to convert from 2003 to 2007/10 and I don't really want to do that.
Is there a way to mimic the "Attachment" data type in 2003? The OLE Object just doesn't not compare to the ease of use (for a End User).
Alternativly I did convert the database from 2003 to 2007 but then all my DAO command like (.edit) brings up a compile error.
I tried to add the Microsoft DAO 3.6 Object Libary but that either clashes with existing lib or if I remove other libs, it still doesn't compile my .edit commands.
Any help please?
Thanks
Pierre
PS: This is how I typically script my DAO routines:
Set db = CurrentDb()
Set rec = db.OpenRecordset("USysPatch", dbOpenDynaset)
With rec
.MoveFirst
.Edit
!Path = NewPath1
.Update
End With
rec.Close
Set rec = Nothing
I still prefer to use 2003, but I need to add some functionality to an existing database which could really use the new "Attachment" data type in 2007/10.
However, that means I have to convert from 2003 to 2007/10 and I don't really want to do that.
Is there a way to mimic the "Attachment" data type in 2003? The OLE Object just doesn't not compare to the ease of use (for a End User).
Alternativly I did convert the database from 2003 to 2007 but then all my DAO command like (.edit) brings up a compile error.
I tried to add the Microsoft DAO 3.6 Object Libary but that either clashes with existing lib or if I remove other libs, it still doesn't compile my .edit commands.
Any help please?
Thanks
Pierre
PS: This is how I typically script my DAO routines:
Set db = CurrentDb()
Set rec = db.OpenRecordset("USysPatch", dbOpenDynaset)
With rec
.MoveFirst
.Edit
!Path = NewPath1
.Update
End With
rec.Close
Set rec = Nothing