IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

can't get SELECT parameters to work on mapforce 2013 x64 Options · View
ultrabeet
Posted: Monday, September 30, 2013 3:05:07 PM
Rank: Advanced Member

Joined: 8/19/2012
Posts: 149
Location: Ireland
Hi All,

I have been using Mapforce 2012 for complex database mappings for a while and I thought I will simplify everything by going for Mapforce 2013.

But here's the trick, I can't get SELECT parameters to work there.

Any ideas what I might be doing wrong?

Mapforce 2013 R2 sp2 x64 + mysql-connector-java-5.1.26-bin


ultrabeet attached the following image(s):
CaptureMF2013X64.PNG

vlad
Posted: Monday, September 30, 2013 3:47:39 PM
Rank: Advanced Member

Joined: 12/13/2005
Posts: 2,856
Location: Mauritius
auto-detect of a parameter type makes often problems with different drivers. I'm always entering a type of parameter. Just a guess.
pfisher44
Posted: Monday, September 30, 2013 5:33:25 PM
Rank: Advanced Member

Joined: 8/29/2012
Posts: 146
Location: atlanta
Was the functionality working on the prior version ?
If you have a spare machine / VM, install the older version try the same situation. It would remove the potential issue of the upgrade you did.
ultrabeet
Posted: Tuesday, October 1, 2013 9:58:44 AM
Rank: Advanced Member

Joined: 8/19/2012
Posts: 149
Location: Ireland
vlad, changing the data type does not affect the behavior.

pfisher44, I was using 2012 rel. 2 sp1 previously. It did not have this feature at all.

I also tried the x32 and it does not seem to work either.

Maybe I am missing something... Has anyone of you used JDBC on 2013 R2 sp2 and tried to put in arguments in the select statement?
vlad
Posted: Wednesday, October 2, 2013 9:48:55 AM
Rank: Advanced Member

Joined: 12/13/2005
Posts: 2,856
Location: Mauritius
Time to stop guessing and contact Altova Support
ultrabeet
Posted: Thursday, October 3, 2013 7:47:52 AM
Rank: Advanced Member

Joined: 8/19/2012
Posts: 149
Location: Ireland
Altova support confirmed they were able to reproduce the problem.

It has been forwarded on to the development team for further investigation.

I will update you once I get a response from them.
eamankwahmanu
Posted: Friday, January 24, 2014 4:37:41 PM
Rank: Member

Joined: 2/5/2013
Posts: 27
Location: Colorado
Hello ultrabeet ,

Have you had any updates on this since your last post. I was just wondering because I need to use such a functionality in my mapping and it seems I was getting the same error.

Please let me know how far you got with it
ultrabeet
Posted: Monday, January 27, 2014 10:11:56 AM
Rank: Advanced Member

Joined: 8/19/2012
Posts: 149
Location: Ireland
eamankwahmanu,

There seem to be JDBC compatibility issues, so some funcionality has just been taken out of Mapforce in the latest release.

Look for 43126 in https://www.altova.com/releasenotes

If you can't find it - it is not fixed yet...

That is the only reason why i am still using mapforce 2012 ;)
Users browsing this topic
guest

Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.