The include file uses an implicit connection. With file-based
sources (like
text files, Excel, and Access), you can often just pass the
path, and ADO
will figure out what's going on without your intervention.
That doesn't
mean it's generally a good idea. ;)
"davebusey" <webforumsuser@macromedia.com> wrote in
message
news:eub682$5pj$1@forums.macromedia.com...
> right, thanks i see.
> i have used this string:
> Provider=Microsoft.ACE.OLEDB.12.0;Data
> Source=C:\myFolder\myAccess2007file.accdb;Persist
Security Info=False;
Looks OK, but I've never seen that provider before. But I
know MS has been
trying to ditch JET, so that makes sense.
> i have tried to replace the source code such that it
points to my local
> copy:
> Source=Macintosh HD:Users:Dave
> Bursey:premierteamsports:htdocs:accessproject.mdb
>
> that didnt work!
> I have no ability to read access files on this machine
(iMac) will this be
> an
> issues?
I don't know if you'll be able to do this on a mac. You'd
have to track
down some mac providers for Access (they can be OLE DB or
ODBC). I'm not
sure how you'd specify the path, either. It would make sense
to do it the
same way you would anywhere else on the mac, but I don't know
if there's
something going on under the covers kind of like on old Win
95 machines.