SendKeys stopped working when upgrading from 7.6.200 to 7.6.300

[nablainc]

A client has begun to bring his MACOLA installation more up to date and has upgraded from Progression 7.6.200 to 7.6.300. (Running MS SQL).

Flexibilty routines seem to start but the Sendkeys function
does not work. (The Flexibilty server and clients have been updated.)

Has anyone any ideas? Should he try upgrading to 7.6.400?

Thanks

Jerzy

 

[nablainc]

It would probably be more accurate to say that SendKeys
fails in some lines of code but appears to work in other places.

Tomorrow I'll try adding the "Wait" parameter = true to see if that helps.

Jerzy

 

[dgillz]

I would go all the way to 7.7.200. 7.6.300 is still 4-1/2 years old! Did you upgrade Flex as well? There is a new Flex cd with 7.6.300, but you can't order or download it anymore.

If you want to post the code I can test it for you in 7.7.200.

Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:

http://www.gainfocus.biz/exceladdin.html

 

[nablainc]

We have had trouble with the Visual Basic Sendkeys not working consistently in this application, so we bought
a routine several years ago from M8 Software that replaces the Visual basic Sendkeys with a routine called "SendKey".
This routine has worked flawlessly until the upgrade to Progression 7.6.300c.

The application is used in the Features/Options screens of Order Entry.

On the BMSELOPT screen (Feature Selection), SendKey "{tab}"
works OK. (However, SendKeys "{tab}" does not work.) On the next screen, BMVALOPT (Validate Options), SendKey "{esc}" and SendKey "{enter}" no longer work.

We have tried adding wait time to the Sendkey function, but it didn't help. Also using Sendkeys with Wait = true did not work.

My client is going to take another step in the upgrade process (after month end closing) to 7.6.400 and I hope
SendKey or Sendkeys will work after that upgrade.

I have to check several other Flexibilty routines that use Sendkeys to see if there are other forms on which it is now failing.

Jerzy

 

[NEmacGuy]

DGilz is correct. Why upgrade to a version that is old. At the very least, review a list of the bugs that are fixed at version 7.6.400a,b,7.7,7.7.100,7.7.200. Then rethink the upgrade. On the oposite side, also check the list of new features, and requirements.

 

[nablainc]

My client intends to continue the upgrade process up to the latest version. He wants to be sure his installation is stable with one version before going to the next higher version.

One thing that bothers us: when the Flexibilty client module is updated, the opening splash screen displays
"Flexibilty Client 7.6.100", not 7.6.300. How can we be sure that Flexibilty 7.6.300 has been installed? I am not at client's, so I don't have any version numbers or file dates to give right now.

Thanks for the suggestions.

Jerzy

 

[nablainc]

We have some Flexibilty code behind a Bill Of Material module form (Product Structure File Maintenance). In that routine SendKey ("{enter}") works OK.

Jerzy

 

[stravis]

I have an executable that you can use to replace the Flexibility (VBA) SendKeys command. It works much more consistently and you can pass the SendKeys parameters and a wait period as parameters to the executable. If you would like a copy of the solution, I would be happy to provide it. Please send an email to stravis{at}enterpriseexpressions.com and I will provide you with a copy.

Scott Travis
Enterprise Expressions LLC

 

[dgillz]

Scott,

I would be very interested in this.

Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:

http://www.gainfocus.biz/exceladdin.html