LittleSmudge
Programmer
I have a number of MSAccess front end apps with data on a MySQL server database. The Roleup patch 1 for SP4 has caused all sorts of mayhem among these applications. Printing problems, Form Closing problems, Can't update combo boxes etc.
I have narrowed the cause down to the one specific update - but unfortunately it is a big roll up hotfix.
I have even downloaded the version 2 of this that MS themselves issues when the first version killed all sorts of other things. ( V2 is a bit better - but it still crashes the apps on a regular basis. )
Uninstalling the update enabled the apps to work fine.
I have two questions.
1) Is there a way to con the individual PCs into thinking that ther update has been done when it hasn't sop that Autoupdate doesn't just keep putting this offending patch back in ?
2) Is there a way of getting to the individual components of the big patch and, by a process of elimination, identifying which single bit is the problem ?
G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
I have narrowed the cause down to the one specific update - but unfortunately it is a big roll up hotfix.
I have even downloaded the version 2 of this that MS themselves issues when the first version killed all sorts of other things. ( V2 is a bit better - but it still crashes the apps on a regular basis. )
Uninstalling the update enabled the apps to work fine.
I have two questions.
1) Is there a way to con the individual PCs into thinking that ther update has been done when it hasn't sop that Autoupdate doesn't just keep putting this offending patch back in ?
2) Is there a way of getting to the individual components of the big patch and, by a process of elimination, identifying which single bit is the problem ?
G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.