I just learned, much to my disappointment, that the order parameters are added to a command object has to be the same as the order they are declared in the SQL Server stored procedure...
Being able to determine the parameter order easily programatically would make things much easier. Any ideas?
Access 2010, SQL Server 2008 R2, Microsoft AtiveX Data Objects 2.8 Library
Naturally the point of the procedure that is saving a record is to avoid SQL injection possibilities and prepare for future move to other Web user interface.
The purpose: I am trying to generically loop through controls on a screen and call the command with added parameters as opposed to having to know up front. Since I have a recordset for reading that has the column order which is the parameter order, I can in theory build my statement that way but would rather avoid it. -I may have fields/columns not on the screen in the recordset.
Being able to determine the parameter order easily programatically would make things much easier. Any ideas?
Access 2010, SQL Server 2008 R2, Microsoft AtiveX Data Objects 2.8 Library
Naturally the point of the procedure that is saving a record is to avoid SQL injection possibilities and prepare for future move to other Web user interface.
The purpose: I am trying to generically loop through controls on a screen and call the command with added parameters as opposed to having to know up front. Since I have a recordset for reading that has the column order which is the parameter order, I can in theory build my statement that way but would rather avoid it. -I may have fields/columns not on the screen in the recordset.