Append query, "invalid password"

I found similiar issues in MS-KB but nothing that helped
me; got the Windows and Office updates from the MS website
but that hasn't changed the behavior of this problem, and
I don't see anything relevant in the newsgroup; help will
be gratefully received.

Windows 2000 system, I'm logged in with admin rights, using
Office 2003. I have two databases on my local drive, in
the same subdirectory. In the database HAMCHEESE, I create
an append query to write records to the db BREAD. Both of
these dbs have the same on-open password (call it MUSTARD.)

When the opening password is on, the append query from
HAMCHEESE tries to write certain records to BREAD, but
is unable, and I get an error: "invalid password."

Removing the password from BREAD lets the append query run
without problem. But we'd rather not have these dbs unprotected
and I'd rather not have to remove the pw each time I run the
query and then replace it.

Anybody? Please? TIA!

_______________________________________________
Ken Kuzenski AC4RD kuzen001 at acpub .duke .edu
_______________________________________________
All disclaimers apply, see? www.duke.edu/~kuzen001

[MGFoster]

ku******@duke.edu wrote:

I found similiar issues in MS-KB but nothing that helped
me; got the Windows and Office updates from the MS website
but that hasn't changed the behavior of this problem, and
I don't see anything relevant in the newsgroup; help will
be gratefully received.

Windows 2000 system, I'm logged in with admin rights, using
Office 2003. I have two databases on my local drive, in
the same subdirectory. In the database HAMCHEESE, I create
an append query to write records to the db BREAD. Both of
these dbs have the same on-open password (call it MUSTARD.)

When the opening password is on, the append query from
HAMCHEESE tries to write certain records to BREAD, but
is unable, and I get an error: "invalid password."

Removing the password from BREAD lets the append query run
without problem. But we'd rather not have these dbs unprotected
and I'd rather not have to remove the pw each time I run the
query and then replace it.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Not sure about this, but I believe you can include the password in the
query like this:

UPDATE TableName In "C:\My Documents\myDB.mdb;PWD=password"
SET ColumnName = NewValue
WHERE <criteria>
--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQH2aoIechKqOuFEgEQJlMQCfY97adUBabIxPgnyCGYUnJI mucbkAn11H
8SG3g568esrge1+tKKbVyjd2
=KYK9
-----END PGP SIGNATURE-----

MGFoster <[e-mail]> wrote:

ku******@duke.edu wrote:

HAMCHEESE tries to write certain records to BREAD, but
is unable, and I get an error: "invalid password."

Not sure about this, but I believe you can include the password in the
query like this:
UPDATE TableName In "C:\My Documents\myDB.mdb;PWD=password"

Thanks, MG, but I'm including it already; Access generated
this syntax so I've been assuming it's correct:

INSERT INTO [;PWD=mustard].tblPFTs ( MRN, TestDate, FVC, FEV1, TLC, FRC,
Unc_DLCO, DLCO, Pct_FVC, Pct_FEV1, Pct_TLC, Pct_FRC, Pct_Unc_DLCO,
Pct_DLCO, VA, Hgb, Done_at, PFT_note, Includeme, AddedBy ) IN
'C:\REFRIGERATOR\BREAD.mdb'[;PWD=mustard]
SELECT [TBLNames].MRN, [TblPFTs].TestDate, [TblPFTs].FVC, [TblPFTs].FEV1,
[TblPFTs].TLC, [TblPFTs].FRC, [TblPFTs].Unc_DLCO, [TblPFTs].DLCO,
[TblPFTs].Pct_FVC, [TblPFTs].Pct_FEV1, [TblPFTs].Pct_TLC,
[TblPFTs].Pct_FRC, [TblPFTs].Pct_Unc_DLCO, [TblPFTs].Pct_DLCO,
[TblPFTs].VA, [TblPFTs].Hgb, [TblPFTs].Done_at, [TblPFTs].PFT_note,
[TblPFTs].Includeme, "App qry" AS Expr1
FROM [TBLNames] LEFT JOIN [TblPFTs] ON [TBLNames].Pat_ID =
[TblPFTs].Pat_ID
WHERE ((([TblPFTs].Exportme)=True));
_______________________________________________
Ken Kuzenski AC4RD kuzen001 at acpub .duke .edu
_______________________________________________
All disclaimers apply, see? www.duke.edu/~kuzen001

[MGFoster]

ku******@duke.edu wrote:

MGFoster <[e-mail]> wrote:

ku******@duke.edu wrote:

HAMCHEESE tries to write certain records to BREAD, but
is unable, and I get an error: "invalid password."

Not sure about this, but I believe you can include the password in the
query like this:
UPDATE TableName In "C:\My Documents\myDB.mdb;PWD=password"

Thanks, MG, but I'm including it already; Access generated
this syntax so I've been assuming it's correct:

INSERT INTO [;PWD=mustard].tblPFTs ( MRN, TestDate, FVC, FEV1, TLC, FRC,
Unc_DLCO, DLCO, Pct_FVC, Pct_FEV1, Pct_TLC, Pct_FRC, Pct_Unc_DLCO,
Pct_DLCO, VA, Hgb, Done_at, PFT_note, Includeme, AddedBy ) IN
'C:\REFRIGERATOR\BREAD.mdb'[;PWD=mustard]
SELECT [TBLNames].MRN, [TblPFTs].TestDate, [TblPFTs].FVC, [TblPFTs].FEV1,
[TblPFTs].TLC, [TblPFTs].FRC, [TblPFTs].Unc_DLCO, [TblPFTs].DLCO,
[TblPFTs].Pct_FVC, [TblPFTs].Pct_FEV1, [TblPFTs].Pct_TLC,
[TblPFTs].Pct_FRC, [TblPFTs].Pct_Unc_DLCO, [TblPFTs].Pct_DLCO,
[TblPFTs].VA, [TblPFTs].Hgb, [TblPFTs].Done_at, [TblPFTs].PFT_note,
[TblPFTs].Includeme, "App qry" AS Expr1
FROM [TBLNames] LEFT JOIN [TblPFTs] ON [TBLNames].Pat_ID =
[TblPFTs].Pat_ID
WHERE ((([TblPFTs].Exportme)=True));

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That looks incorrect. It looks as if the string ";PWD=mustard" has been
defined as a table! I'd change the INSERT INTO clause to this:

INSERT INTO tblPFTs IN "C:\REFRIGERATOR\BREAD.mdb;PWD=mustard"
( MRN, TestDate, FVC, FEV1, TLC, FRC, Unc_DLCO, DLCO, Pct_FVC, Pct_FEV1,
Pct_TLC, Pct_FRC, Pct_Unc_DLCO, Pct_DLCO, VA, Hgb, Done_at, PFT_note,
Includeme, AddedBy )

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQH7cKYechKqOuFEgEQJUtQCfVp3z5WJ2VNFYmOW2HSKTfv FQ+A4AoJNq
3TYdvnmax/y8fsMACZizQsUF
=v/iM
-----END PGP SIGNATURE-----

MGFoster <[e-mail]> wrote:

That looks incorrect. It looks as if the string ";PWD=mustard" has been
defined as a table! I'd change the INSERT INTO clause to this:

THank you very much, MG! I assumed that the string
that Access generated would be correct--I'll give this
a try in the morning. Thanks!

--Ken
_______________________________________________
Ken Kuzenski AC4RD kuzen001 at acpub .duke .edu
_______________________________________________
All disclaimers apply, see? www.duke.edu/~kuzen001

[CDB]

I have been working on an almost identical problem; here is my solution -

SELECT Count(Contracts.ContractNo) AS UnitsSold
FROM Contracts
IN "" [MS Access;DATABASE=C:\....Data.mdb;PWD=.....;]
WHERE (Contracts.ContractDate etc ;

This format is one of several in the IN Clause Help, but it was not clear
that it applied to the above situation.

Clive

<ku******@duke.edu> wrote in message
news:c5**********@gargoyle.oit.duke.edu...

MGFoster <[e-mail]> wrote:

That looks incorrect. It looks as if the string ";PWD=mustard" has been
defined as a table! I'd change the INSERT INTO clause to this:

THank you very much, MG! I assumed that the string
that Access generated would be correct--I'll give this
a try in the morning. Thanks!

--Ken
_______________________________________________
Ken Kuzenski AC4RD kuzen001 at acpub .duke .edu
_______________________________________________
All disclaimers apply, see? www.duke.edu/~kuzen001

CDB <al***@delete.wave.co.nz> wrote:

I have been working on an almost identical problem; here is my solution -

Clive, thanks so much! That's two things to try
this morning--I appreciate it!
_______________________________________________
Ken Kuzenski AC4RD kuzen001 at acpub .duke .edu
_______________________________________________
All disclaimers apply, see? www.duke.edu/~kuzen001

CDB <al***@delete.wave.co.nz> wrote:

FROM Contracts
IN "" [MS Access;DATABASE=C:\....Data.mdb;PWD=.....;]
WHERE (Contracts.ContractDate etc ;

I tried this version first and it works perfectly.

Many, many thanks to Clive and MG for the help!

I know now that I can't depend on syntax to be correct
just because Access generates it. :->

THANKS!

--Ken

_______________________________________________
Ken Kuzenski AC4RD kuzen001 at acpub .duke .edu
_______________________________________________
All disclaimers apply, see? www.duke.edu/~kuzen001