I've just installed Forms version 10 and started some development work on a form.  I've already come across a small issue using Lookup Rules.  I'm not sure if it specific to v.10 or not.  When I initially set up a lookup rule that utilized a stored procedure with 3 parameters it listed the parameters in the wrong order.  It took me a bit to figure out what the issue was.  I ended up recreating the lookup rule and the second time it put the parameters in the correct order.  Nothing had changed with the stored procedure.

I noticed that the lookup rule calls the stored procedure using parameters in order without using the parameter name in the call.  I'm not sure why this was done, but I think using the parameter name in the call would be a better practice.  If a developer reorders the parameters in a stored procedure without making any other changes this will break a Forms Lookup Rule.  I'm curious what others think.  Should this be an enhancement request?

Info from Microsoft: https://technet.microsoft.com/en-us/library/ms177436(v=sql.105).aspx

Values can be passed to stored procedures either by explicitly naming the parameters and assigning the appropriate value or by supplying the parameter values given in the CREATE PROCEDURE statement without naming them. For example, if the stored procedure my_proc expects three parameters named @first, @second, and @third, the values passed to the stored procedure can be assigned to the parameter names, such as:

EXECUTE my_proc @second = 2, @first = 1, @third = 3;

Or by position without naming them:

EXECUTE my_proc 1, 2, 3;

Naming the parameters when executing the stored procedure allows the parameters to be supplied in any order.