fturner64119
asked on
Access 2003 Runtime Error with Runtime - Function not available in expressions
Hi Folks,
Sometimes I just want to eat worms!
I am trying to use the Access 2003 runtime. I have a program that is
fully working in 2003 but when I install the runtime version onto a machine
that has no MS Access with O/S Win 2000 installed, I have multiple errors.
error --- "Function is not available in query expressions.
The function is format([event_date],"ddd")
This error occurs 30 times, as I used it alot in queries.
There are four other errors for simple functions I use in the 2003
program. Has anyone had similar errors or can anyone point me to a
site that is likely to look into Access 2003 Runtime bugs. Have tried
searching the Microsoft site without success. I cannot believe I am
the only one experiencing these problems.
Any help greatley appreciated
Sometimes I just want to eat worms!
I am trying to use the Access 2003 runtime. I have a program that is
fully working in 2003 but when I install the runtime version onto a machine
that has no MS Access with O/S Win 2000 installed, I have multiple errors.
error --- "Function is not available in query expressions.
The function is format([event_date],"ddd")
This error occurs 30 times, as I used it alot in queries.
There are four other errors for simple functions I use in the 2003
program. Has anyone had similar errors or can anyone point me to a
site that is likely to look into Access 2003 Runtime bugs. Have tried
searching the Microsoft site without success. I cannot believe I am
the only one experiencing these problems.
Any help greatley appreciated
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
turner64119
What was the exact resolution - per the possibilities mention in the KB ... for your case?
mx
What was the exact resolution - per the possibilities mention in the KB ... for your case?
mx
ASKER
Oh man, has this one been a trip!
tks DatabaseMX but I did have a DAO reference already.
tks jpauline, you lead me down a path that really help out on this one.
The article you pointed me to had a lot to sy about references. Like, uncheck them, Compile, do a Compact and repair, leave the program, reenter the program and reset the references. After I did this I still had problems, I put the references in a different order. Now I'm seeing light ! But the real deal came when I did NOT make a .mde and used the package wizard with the .mdb. Big Change. The code started runing a bit and then pooped out. It wanted some files it could not find. Don't ask me why, I though the wizard was supposed to add all necessay files.
In my case the files where MSADO27.tbl -- MSOUTL.OLB and MSWORD.olb. So, I simply added these files in the wizard setup (add files), set it to my newered PC and bingo. These files where in \WINNT\SYSTEM32.
I reckon it's a done deal. Let ya'all know how it goes in with the clients.
tks fturner64119
tks DatabaseMX but I did have a DAO reference already.
tks jpauline, you lead me down a path that really help out on this one.
The article you pointed me to had a lot to sy about references. Like, uncheck them, Compile, do a Compact and repair, leave the program, reenter the program and reset the references. After I did this I still had problems, I put the references in a different order. Now I'm seeing light ! But the real deal came when I did NOT make a .mde and used the package wizard with the .mdb. Big Change. The code started runing a bit and then pooped out. It wanted some files it could not find. Don't ask me why, I though the wizard was supposed to add all necessay files.
In my case the files where MSADO27.tbl -- MSOUTL.OLB and MSWORD.olb. So, I simply added these files in the wizard setup (add files), set it to my newered PC and bingo. These files where in \WINNT\SYSTEM32.
I reckon it's a done deal. Let ya'all know how it goes in with the clients.
tks fturner64119
mx