Dont buy Office 2002

[Guest_imported]

Dont buy Office 2002, full of CRITICAL BUGS.
I lost much time in migration for nothing...
Changes practily only the interface, in the rest plus more and much more bugs...

EX: ACCESS 2002 DONT UNDERSTAND Sql 2000 DECIMAL FIELDS, if you use it, your SUM queries dont work properly.

Outlook 2002 Macro Security dont allow other application to send messages automatic
Ex: Wireless secretary cant send your emails without an slow confirmation, with low security already selected...
Forcing us to use Mobile Wireless from Microsoft that works only with Exchange SErvers

And ETC....

Try and see your selves (If you have time to lose)

 

[Guest_imported]

The Outlook problem seems to be solved certifying your code
(maybe)

 

[butchrecon]

Office 2002? Are you talking Office XP or Office for MAC? Please let us (Tek-tips members) know if the solutions we provide are helpful to you. Not only do they help you but they may help others.


James Collins
Computer Hardware Engineer
A+, MCP

email: butchrecon@skyenet.net

 

[Guest_imported]

Office XP PC

 

[Guest_imported]

I understand... but

I keep the direct contact with Microsoft, and I know, that these problems (they did not know about this critical problem in Access 2002 yet), are only solved with a new MDAC or Hotfix or something seemed, and them it does not have haste in helping to its customers (example: The
errors in Access 2000: several months had launched a SP1 after), and I am speaking really of critical errors. This problem becomes impossible the migration for Access 2002. It gives the printing that they do not test more the programs before launching.

I will submit the problem (the same letter I send to Microsoft)

 

[Guest_imported]

Access 2002 SQL Server 2000
Im working in an a .adp

Ex:

The Table: PRICES

COD_PROD INT
PRICE NUMERIC(18,4)

Create 2 views

The first query:

SELECT * FROM PRICES

Works well, the both values are numbers

The second query:

SELECT SUM(PRICE) AS Expr1 FROM PRICES

The result is in STRING FIELD

Conclusion: In Access 2002, All your queries with DECIMAL FIELDS AND SUM(), OR AVG() DONT WORK PROPERLY BECAUSE THE RESULTS ARE IN STRING (DO YOU MAYBE HAVE DECIMAL ERRORS)

 

[Guest_imported]

THE RESPONSE FOR MICROSOFT:

Hi Lisandro,

The issue you are experiencing has already been documented and is currently
being addressed. I am unsure if there will be any hotfix/service pack/mdac
update etc. at this time. Any information will be made available as a
public article from our website.

Currently the workaround is to use the sample I have provided and convert
any aggregate function result back to the datatype you wish.

e.g.

SELECT CONVERT(numeric(18, 4), SUM(price)) AS Expr1
FROM dbo.Table1

Unfortunately, if it is prohibitive to use the workaround due to the great
amount of changes, I would recommend reverting to Access 2000.



HTH

Thank you for working with Microsoft Developer Support for Access,

Felix Lima, MCP
Microsoft Access Support Professional

 

[Guest_imported]

Any MCP can anwser my collocations?

 

[Guest_imported]

This problem dont have solution

 

[Guest_imported]

The problem in Outlook 2002 its a but too

 

[iSeriesCodePoet]

I have been using Outlook XP beta for about a month now and have not had any major problems. The problem I had was sending a distribution list to someone else. Please let us (Tek-Tips members) know if the solutions I provide are helpful to you. Not only do my posts help you but they may help others.

Mike Wills
IT Corporate Support
RPG Programmer
koldark@koldark.net

 

[conceptumator]

I updated from Office 2000 to XP a few weeks ago and love it; no problems whatsoever. NOTE: the RAM requirements for XP are different than in the past. It needs a MINIMUM of 128 MB PLUS 8 MB for each program you have open; that means you need to bite the bullet and go to at least 256 MB. There are many places on line right now where you can get a 256 MB PC133 chip for $50 if you do some shopping.

 

[Guest_imported]

If you are an operator user, maybe work fine, but try use advanced features and you see, in the Access 2002 the problem is in .ADP with SQL Server 2002, decimal fields, in the Outlook is: if you make an programs that send emails (example), after set security to minimal, they still showing security messages and stoping your program....

Thanks...