B
Bob Vance
All my Dates in my friends access db are erroring now that my friend has
windows 7 Installed, Has anyone heard about this???
windows 7 Installed, Has anyone heard about this???
All my Dates in my friends access db are erroring now that my friend has
windows 7 Installed, Has anyone heard about this???
Going by my friends screen shoots of my db, It is erroring
Function is not available in Expressions in query expression
Format([HorseDate],"dd-mmm-yy".
12 errors and they all finish with a dot and not a bracket is this normal???
Regards Bob
John W. Vinson said:Going by my friends screen shoots of my db, It is erroring
Function is not available in Expressions in query expression
Format([HorseDate],"dd-mmm-yy".
12 errors and they all finish with a dot and not a bracket is this
normal???
Regards Bob
I have no idea; I don't have Win7 and have no immediate intention to
install
it.
Thanks John but what happens when you buy a new machine that has win7 pre
loaded
Going by my friends screen shoots of my db, It is erroring
Function is not available in Expressions in query expression
Format([HorseDate],"dd-mmm-yy".
12 errors and they all finish with a dot and not a bracket is this
normal??? Regards Bob
I have no idea; I don't have Win7 and have no immediate intention
to install it.
I'll cross that bridge when I get to it.
Sorry if my response sounded like criticism of you - that wasn't
the intent at all! I'm simply saying that "I Don't Know" and can't
give you any advice, because I don't have Win7 and cannot do any
testing. Apologies if it came across as anything other than that!
David W. Fenton said:Going by my friends screen shoots of my db, It is erroring
Function is not available in Expressions in query expression
Format([HorseDate],"dd-mmm-yy".
12 errors and they all finish with a dot and not a bracket is this
normal??? Regards Bob
I have no idea; I don't have Win7 and have no immediate intention
to install it.
Windows 7 does not cause any more reference problems than any other
version of Windows.
If everyone would avoid adding any references other than the base
three (Access, VBA and DAO), they'd not run into these problems.
Late binding allows the use of all sorts of external libraries
without exposing the app to the broken reference problem.
I can't see why anyone would ever add references to anything other
than those basic three, except perhaps naivete, or laziness.
Bob Vance said:Ok my Coder not me as I dont have enough experience with References
Changed
Visual Basic For Application
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
Microsoft DAO 3.6 Object Library
For these:
Visual Basic For Application
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
Microsoft Visual Basic for Application Extensilbilty 5.3
Microsoft Outlook 12 Object Library
Microsoft Office 12.0 Access database engine Object Library
I have added a email code to outlook and I suspect one of these 3 new
references is not liked by Win7 !!
I am currently testing with my friend with Win7 which one it is
I tried that thanks Douglas but now erroring on: Dim recHorseID As NewAs David suggests, try using just
- Visual Basic For Application
- Microsoft Access 12.0 Object Library
- Microsoft Office 12.0 Access database engine Object Library
Use Late Binding rather than setting a reference to Microsoft Outlook 12
Object Library.
Bob Vance said:I tried that thanks Douglas but now erroring on: Dim recHorseID As New
ADODB.Recordset
I tried that thanks Douglas but now erroring on: Dim recHorseID
As New ADODB.Recordset
Visual Basic For Application
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
Microsoft DAO 3.6 Object Library
For these:
Visual Basic For Application
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
Microsoft Visual Basic for Application Extensilbilty 5.3
Microsoft Outlook 12 Object Library
Microsoft Office 12.0 Access database engine Object Library
Why do you think you need this one?
Use late binding with Outlook to avoid needing a reference. If you
do that, all your non-Outlook code will run on machines without
Outlook installed.
This last is just DAO for A2007.
Dim myitem As Outlook.MailItem
Dim myout As Outlook.Application
Set myout = New Outlook.Application
Set myitem = myout.CreateItem(olMailItem)
David W. Fenton said:Change these to this:
Dim myitem As Object
Dim myout As Object
Set myout = CreateObject(Outlook.Application, "localhost")
Set myitem = myout.CreateItem(olMailItem)
...and hyou should be set.
The key is that you don't use any of the Outlook data types, and use
object variables instead.
Douglas J. Steele said:He'll also need to fix the line of code
Set myitem = myout.CreateItem(olMailItem)
Either change it to
Set myitem = myout.CreateItem(0)
or else add a declaration of the olMailItem constant
Const olMailItem As Long = 0