No values after UNION (Service Pack 3 problem)

B

Bart E

Hi all,

After performing a UNION I have no values but
some weird signs.
This is the statement:

1)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct.[SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], NULL as [BUD_AI], NULL as
[BUD_NET_SALES], NULL as [BUD_GM], NULL as
[BUD_NET_SALES_LC]
FROM SumAct, SumBud;
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumAct, SumBud;

I've corrected the problem, this is the statement:

2)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct.[SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], '0' as [BUD_AI], '0' as
[BUD_NET_SALES], '0' as [BUD_GM], '0' as
[BUD_NET_SALES_LC]
FROM SumAct
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumBud;

So instead of using NULL I used '0' to correct the problem.
On a computer running W2K,Service Pack 1 or 2 and Access
2000 the first query runs fine.
After SP3 is installed the first query returns some weird
signs. When I use the second query the results are OK.

Does anybody encountered the same problem and has a fixed
solution (so I don't have apply changes to other queries)?
Which changes are deployed in SP3.

Note: When the first query is performed on a WIN XP
computer I have the same problem.

Thanks in advance.

Kind regards,
Bart
 
B

Bart E

Lowland,

Thanks for the quick reply.
The acwz* files haven't been renamed, but
I think this is not necessary to do because
created and modified date are the same (august 2000).
Maybe I'm wrong ?

Tomorrow I'll ask my admin to do a new install of SP3 after
I renamed the acwz*.mde files to OLD.

Regards,
Bart

-----Original Message-----
Just a thought

Did you rename the three acwz* files in C:\Program Files\Microsoft
Office\Office\1033 to "old" prior to upgrade

Also, did you do a complete recache and reinstall?

Don't know if this is the issue...

Lowland
Bart E said:
Hi all,

After performing a UNION I have no values but
some weird signs.
This is the statement:

1)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct.[SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], NULL as [BUD_AI], NULL as
[BUD_NET_SALES], NULL as [BUD_GM], NULL as
[BUD_NET_SALES_LC]
FROM SumAct, SumBud;
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumAct, SumBud;

I've corrected the problem, this is the statement:

2)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct.[SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], '0' as [BUD_AI], '0' as
[BUD_NET_SALES], '0' as [BUD_GM], '0' as
[BUD_NET_SALES_LC]
FROM SumAct
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumBud;

So instead of using NULL I used '0' to correct the problem.
On a computer running W2K,Service Pack 1 or 2 and Access
2000 the first query runs fine.
After SP3 is installed the first query returns some weird
signs. When I use the second query the results are OK.

Does anybody encountered the same problem and has a fixed
solution (so I don't have apply changes to other queries)?
Which changes are deployed in SP3.

Note: When the first query is performed on a WIN XP
computer I have the same problem.

Thanks in advance.

Kind regards,
Bart
Click to expand...


.
Click to expand...
 
L

Lowland

MS says....
Office 2000 SP3 and Microsoft Access

If Access 2000 is installed on client computers that use the administrative
image, you will need to carry out the following steps before recaching and
reinstalling Office 2000 SP3.

1.. Locate the three acwz*.mde files on the client computers. The English
version of Office 2000 installs these files in C:\Program Files\Microsoft
Office\Office\1033 by default. The files are: acwztool.mde, acwzmain.mde,
and acwzlib.mde.


2.. Rename the three files from acwz*.mde files to acwz*.old, keeping the
files in the same location. You can do this by right-clicking each file,
selecting Rename, and typing the new file name. Or, in the command line, you
can type ren acwz*.mde acwz*.old.


3.. Update the existing client installations using the instructions listed
below.
Running the installation script
To update an existing client installation from an administrative
installation point, run the following command line on the client computer:

start msiexec /i [path to updated .msi file on the admin image]
REINSTALL=[list of features]
UPGRADEWITHRECACHE=TRUE REINSTALLMODE=vomu /qb
Lowland
Lowland said:
Just a thought

Did you rename the three acwz* files in C:\Program Files\Microsoft
Office\Office\1033 to "old" prior to upgrade

Also, did you do a complete recache and reinstall?

Don't know if this is the issue...

Lowland
Bart E said:
Hi all,

After performing a UNION I have no values but
some weird signs.
This is the statement:

1)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct.[SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], NULL as [BUD_AI], NULL as
[BUD_NET_SALES], NULL as [BUD_GM], NULL as
[BUD_NET_SALES_LC]
FROM SumAct, SumBud;
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumAct, SumBud;

I've corrected the problem, this is the statement:

2)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct.[SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], '0' as [BUD_AI], '0' as
[BUD_NET_SALES], '0' as [BUD_GM], '0' as
[BUD_NET_SALES_LC]
FROM SumAct
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumBud;

So instead of using NULL I used '0' to correct the problem.
On a computer running W2K,Service Pack 1 or 2 and Access
2000 the first query runs fine.
After SP3 is installed the first query returns some weird
signs. When I use the second query the results are OK.

Does anybody encountered the same problem and has a fixed
solution (so I don't have apply changes to other queries)?
Which changes are deployed in SP3.

Note: When the first query is performed on a WIN XP
computer I have the same problem.

Thanks in advance.

Kind regards,
Bart
Click to expand...
Click to expand...
 
B

Bart E

Thanks Lowland,

I'll be trying this later on the day and I'll keep
you informed of the result.

Regards,
Bart
-----Original Message-----
MS says....
Office 2000 SP3 and Microsoft Access

If Access 2000 is installed on client computers that use the administrative
image, you will need to carry out the following steps before recaching and
reinstalling Office 2000 SP3.

1.. Locate the three acwz*.mde files on the client computers. The English
version of Office 2000 installs these files in C:\Program Files\Microsoft
Office\Office\1033 by default. The files are: acwztool.mde, acwzmain.mde,
and acwzlib.mde.


2.. Rename the three files from acwz*.mde files to acwz*.old, keeping the
files in the same location. You can do this by right- clicking each file,
selecting Rename, and typing the new file name. Or, in the command line, you
can type ren acwz*.mde acwz*.old.


3.. Update the existing client installations using the instructions listed
below.
Running the installation script
To update an existing client installation from an administrative
installation point, run the following command line on the client computer:

start msiexec /i [path to updated .msi file on the admin image]
REINSTALL=[list of features]
UPGRADEWITHRECACHE=TRUE REINSTALLMODE=vomu /qb
Lowland
Lowland said:
Just a thought

Did you rename the three acwz* files in C:\Program Files\Microsoft
Office\Office\1033 to "old" prior to upgrade

Also, did you do a complete recache and reinstall?

Don't know if this is the issue...

Lowland
Bart E said:
Hi all,

After performing a UNION I have no values but
some weird signs.
This is the statement:

1)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct. [SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], NULL as [BUD_AI], NULL as
[BUD_NET_SALES], NULL as [BUD_GM], NULL as
[BUD_NET_SALES_LC]
FROM SumAct, SumBud;
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumAct, SumBud;

I've corrected the problem, this is the statement:

2)
SELECT DISTINCTROW SumAct.[Product Line] as
[PRODUCT_LINE], SumAct.[Product Grp] as [PRODUCT_GROUP],
SumAct.[SD-Code] as [SD_CODE], SumAct.[SD-Name] as
[SD_NAME], SumAct.Area as [AREA], SumAct.PL6_Code_Name as
[PL6_CODE_NAME], SumAct.PL6_Name as [PL6_NAME],
SumAct.SumOfVol as [ACT_AI], SumAct.SumOfNS as
[ACT_NET_SALES], SumAct.SumOfGM as [ACT_GM], SumAct.
[SumOfNS in LC] as [ACT_NET_SALES_LC], SumAct. [SumOfPar on
NS] as [ACT_PARITY_NET_SALES], SumAct.[SumOfPar on Cogs]
as [ACT_PARITY_COGS], '0' as [BUD_AI], '0' as
[BUD_NET_SALES], '0' as [BUD_GM], '0' as
[BUD_NET_SALES_LC]
FROM SumAct
UNION SELECT DISTINCTROW SumBud.[Product Line] as
[PRODUCT_LINE], SumBud.[Product Grp] as [PRODUCT_GROUP],
SumBud.[SD-Code] as [SD_CODE], SumBud.[SD-Name] as
[SD_NAME], SumBud.Area as [AREA], SumBud.PL6_Code_Name as
[PL6_CODE_NAME], SumBud.PL6_Name as [PL6_NAME], NULL,
NULL, NULL, NULL, NULL, NULL, SumBud.SumOfVol as [BUD_AI],
SumBud.SumOfNS as [BUD_NET_SALES], SumBud.SumOfGM as
[BUD_GM], SumBud.[SumOfNS in LC] as [BUD_NET_SALES_LC]
FROM SumBud;

So instead of using NULL I used '0' to correct the problem.
On a computer running W2K,Service Pack 1 or 2 and Access
2000 the first query runs fine.
After SP3 is installed the first query returns some weird
signs. When I use the second query the results are OK.

Does anybody encountered the same problem and has a fixed
solution (so I don't have apply changes to other queries)?
Which changes are deployed in SP3.

Note: When the first query is performed on a WIN XP
computer I have the same problem.

Thanks in advance.

Kind regards,
Bart
Click to expand...
Click to expand...


.
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

No values after UNION (service pack 3 problem ??) 0

Top