|
Posted by Matt Hurst on September 22, 2008, 6:23 pm
Please log in for more thread options
After aplying all the most recent patches for vista and RMS, I think I found
MS fix for this problem, they just turned off the function for the macro
button. Ctl-F3 doesn't do anything any more, which fixes the previous
problem that it didn't work.
The closest fix I could find for this problem, was to record the macro in
RMS2sp1 on WinXP, then export the macro and macroevent tables with BCP,
manually adjust some of the Time column values so none of the events tried to
fire at the same time, and then replace the macro and macroevent tables on
the vista machine with the backup, then fix the macroid fields in the
macroevent table to line up with their corresponding macro entries .... and
some of the macros would work after that.
"jennydat" wrote:
> 2.0.0117 I think, that's the latest one as far as I know.
> 2.0.0116 was the service pack one.
> --
> Jenny
>
>
> "root" wrote:
>
> > Jenny,
> >
> > Any idea what the latest hotfix brings RMS 2.0 version to?
> >
> > 2.0.01xx
> >
> >
> >
> > > There are a number of issues with Vista and RMS, have you applied the
> > > latest
> > > hotfix for RMS as it was recently released and resolves most of these
> > > issues.
> > >
> > > What version are you currently on?
> > > --
> > > Jenny
> > >
> > >
> > > "Matt Hurst" wrote:
> > >
> > >> I have had trouble replaing macros in RMS2sp1 specifically when a sale
> > >> item
> > >> price change requires a reason code. In vista it seems the macro tries
> > >> to do
> > >> events out of order, when in WinXP it doesn't have that problem. Has
> > >> anyone
> > >> else seen this behavior?
> >
> >
> >
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap