Date() and Now() not working on Vista...shows #NAME?

  • Thread starter Thread starter Rico
  • Start date Start date
R

Rico

Hello,

I have a project that I've created that I'm installing in mde format on
Vista. For some reason, anywhere that Date() or Now() is used is showing up
#NAME?. Any ideas why this might be happening?

Thanks
Rick
 
Hi Gina,

That is the first place I'd check. The problem is, the databse is in MDE
format and the target / test machine does not have Access installed.

I'm using SageKey's MSI wizard which does a brilliant job of installing all
references (I have never had an issue deploying a database and its
references). Having said that, I have a log that generates when references
are missing, and that log is not being generated.

Any other ideas?

Rick
 
Rico,

Okay, yes that is true for .mde. Since this machine is Vista let's check
for if it's in a Trusted Location. Or have you done that already? What
folder does the log get generated to? Perhaps you need to also add that to
Trusted Locations?

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm
 
probably because you're trying to use DAO, and it's no longer
available.

you should have moved to ADO

some people claim that they renamed DAO, but they're full of it

-Aaron
 
never had a problem?

are you kidding me?

it's a simple MDB, you drop it on a machine and it works.. if it
doesn't then you're doing something wrong

what would you possibly need sagekey for?? lol

-aaron
 
Sorry Aaron, that's not an option. Besides, DAO should be installed with
MDAC is that correct?

probably because you're trying to use DAO, and it's no longer
available.

you should have moved to ADO

some people claim that they renamed DAO, but they're full of it

-Aaron
 
[email protected] said:
probably because you're trying to use DAO, and it's no longer
available.
Wrong.

you should have moved to ADO
Click to expand...

Seldom any reason to use ADO.
some people claim that they renamed DAO, but they're full of it
Click to expand...

DAO still exists and works well.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
No. DAO comes with Access. Including the runtime.
Click to expand...

Uh, DAO comes with *Windows*, no? That's why they took it out of the
MDAC, because Jet/DAO were already on every recent copy of Windows
(i.e., Win2K and after).
 
David W. Fenton said:
Uh, DAO comes with *Windows*, no? That's why they took it out of the
MDAC, because Jet/DAO were already on every recent copy of Windows
(i.e., Win2K and after).
Click to expand...

Duhhh. You're correct. I got confused. Somehow.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
Duhhh. You're correct. I got confused. Somehow.
Click to expand...

Of course, it *is* worth pointing out that the version of Jet is 4.0
and the version of DAO 3.6, and if you want to use Jet 5, er, I mean
ACE, you can't do it without installing it explicitly. Access and
the runtime will certainly do that, but I understand there's a
developer's package somewhere that's independent of Access/runtime,
but I've lost the reference (I'd never need it).
 
a) performance
b) portability
c) ability to move to real vb6
d) ability to move to MTS / COM+
e) ability to change databases without rewriting everything

there's lot of reasons, dipshit
 
sorry

DAO and Jet haven't been included with MDAC or Windows for the past
decade

they get installed with Office, and they're not the default Library
for several versions...

-Aaron
 
it's not available in MDAC for many many versions right??

so if I wanted to get Jet 4.0 installed on NT 4, what would I need to
do?

why is it that they didn't include Jet in _ANY_ downloadable package
for many many many years--
and somehow you think that it's the default library?

DAO is ****ing stupid anyone that uses it-- is handcuffed to Jet.

**** Jet thus--- **** DAO.

-Aaron
 
As of version 2.6, MDAC (Microsoft Data Access Components) no longer
include the Jet database engine components.

now.. which version of MDAC ships with Windows XP?

those two statements together--- prove-- that Jet is not available as
a built in component-- with Windows XP.

-Aaron
 
Back
Top