Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SQL2000 Upgrade to SP4
- Thread starter Maz61
- Start date
MacolaHelp
Instructor
I have a couple of 76300+ sites using sp4 & it was fine. Can't tell you about 76400.
Maz61,
I have several customers that have upgraded to the 7.6.400. Only one has also upgraded to SQL2005. The rest are on SQL 2000 service pack 3 and 4. I have not seen any issues.
Tha being said if you do upgrade to 7.6.400 you should apply SPA also.
The list of bug fixes and enhancements is prety long but the biggest changes are the enhanced password capability. This is optional but if you do turn it on you cannot turn it back off. The supervisor document on the Exact website is a must read and does a good job of describing the process. If you need to be Sarbanes Oxley compliant that you will need this.
The other major enhancement is related to credit card processing and encrypting the card number. This is not an option and will change the way that you process credit cards. If you wre using the Exact credit card processing piece there will not be a big problem. The issue is related if you are manually processing the credit card. If you do this and use the OE cash in order entry you no longer will see the card number or be able to change it. There is a key stroke that you can use to view the card but if you want to use a different one you will need to exit the order and then update the customer master with the new card number and then open the order again to finish the process. This is really not a bug but is required to provide the level of security needed. But remember this is only an issue if using the manual OE cash process.
Other that that I have actually heard most clients saying they thought it was running faster but this is always sunjective.
Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.
If the only tool you can use is a hammer then all your problems look like nails.
I have several customers that have upgraded to the 7.6.400. Only one has also upgraded to SQL2005. The rest are on SQL 2000 service pack 3 and 4. I have not seen any issues.
Tha being said if you do upgrade to 7.6.400 you should apply SPA also.
The list of bug fixes and enhancements is prety long but the biggest changes are the enhanced password capability. This is optional but if you do turn it on you cannot turn it back off. The supervisor document on the Exact website is a must read and does a good job of describing the process. If you need to be Sarbanes Oxley compliant that you will need this.
The other major enhancement is related to credit card processing and encrypting the card number. This is not an option and will change the way that you process credit cards. If you wre using the Exact credit card processing piece there will not be a big problem. The issue is related if you are manually processing the credit card. If you do this and use the OE cash in order entry you no longer will see the card number or be able to change it. There is a key stroke that you can use to view the card but if you want to use a different one you will need to exit the order and then update the customer master with the new card number and then open the order again to finish the process. This is really not a bug but is required to provide the level of security needed. But remember this is only an issue if using the manual OE cash process.
Other that that I have actually heard most clients saying they thought it was running faster but this is always sunjective.
Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.
If the only tool you can use is a hammer then all your problems look like nails.
- Thread starter
- #5
- Status
Similar threads