H
hcbph
I've got a problem I'm trying to help a company out on.
Windows XP Pro, Access 2003 in a networked environment.
When in their development area, all parts seem to work.
When they rolled out the 'same' builds into production,
the Find Unmatched Query Wizard no longer works right.
I'm told the only difference is that there are policies
restricting user in some areas, plus users are not local
admins in production, supposedly the hardware and
installs are otherwise the same.
Create 2 tables, 1 field in each with a few records
created in each table. Run the wizard to compare them
for unmatched records and it gives the following in the
development area:
SELECT Table1.name
FROM Table1 LEFT JOIN table2 on Table1.name = table2.name
Where (((table2.asfas) is Null))
On the production machine, same user tries to create the
same tables and query and when it gets to the "Fields in
Table1" vs Fields in Table2, it's blank under 'Fields in
Table1'. Nothing there, can't pick a thing.
He was able to display the sql code on this one somehow:
SELECT (Table).(TEXT1)
FROM (table) LEFT JOIN Table1 on (table).[]=(table1).[]
WHERE ((Table1).[] is Null}}
I had to type this in by hand, so hopefully no typos.
I've compared settings in Access between the 2 PCs and
cannot find a difference. I've tried temporarily making
the user a local admin in the production environment, no
change. I find no possible explanation other than the
possibility of 1 or more policies doing something bad.
Any ideas what it might be or where to look. I'm just
trying to help them out, I am not an Access Expert, just
someone that supported software issues in the past.
Thanks much
Windows XP Pro, Access 2003 in a networked environment.
When in their development area, all parts seem to work.
When they rolled out the 'same' builds into production,
the Find Unmatched Query Wizard no longer works right.
I'm told the only difference is that there are policies
restricting user in some areas, plus users are not local
admins in production, supposedly the hardware and
installs are otherwise the same.
Create 2 tables, 1 field in each with a few records
created in each table. Run the wizard to compare them
for unmatched records and it gives the following in the
development area:
SELECT Table1.name
FROM Table1 LEFT JOIN table2 on Table1.name = table2.name
Where (((table2.asfas) is Null))
On the production machine, same user tries to create the
same tables and query and when it gets to the "Fields in
Table1" vs Fields in Table2, it's blank under 'Fields in
Table1'. Nothing there, can't pick a thing.
He was able to display the sql code on this one somehow:
SELECT (Table).(TEXT1)
FROM (table) LEFT JOIN Table1 on (table).[]=(table1).[]
WHERE ((Table1).[] is Null}}
I had to type this in by hand, so hopefully no typos.
I've compared settings in Access between the 2 PCs and
cannot find a difference. I've tried temporarily making
the user a local admin in the production environment, no
change. I find no possible explanation other than the
possibility of 1 or more policies doing something bad.
Any ideas what it might be or where to look. I'm just
trying to help them out, I am not an Access Expert, just
someone that supported software issues in the past.
Thanks much