Labelling a T-SQL Stored procedure as a database field Follow

0
Avatar
Jason Ruiter

I have a T-SQL stored procedure that returns a serial number. When I create a database field, I can use the "Custom SQL Statement" to call the procedure (exec usp_NextSerialNumber '231C'). I am unable to label it as a database field, so I can't access it from within a Bartender form. What's the proper way to do this?

3 comments

0
Avatar
Jacob Pazitka
Comment actions Permalink

In the stored procedure, does the return value have a label?

0
Avatar
Bob Steele
Moderator
Comment actions Permalink

Jacob,

Is there anyway to use a standard SQL statement to query and pull the correct records or possibly make a view table of the data that you need?  We do not officially support Stored Procedures in Bartender.

 

Thank you,

0
Avatar
Jacob Pazitka
Comment actions Permalink

Bob, that would depend.  The amount of data that a standard view would need to retrieve prior to filtering with the database prompts could be extensive.  This would negatively impact the SQL server as well as require tremendous resources on the Bartender client, and network infrastructure.  

If Bartender passed the prompts into the sql server to allow filtering to be performed on the sql server prior to data retrieval, then that process would be preferred.

It all depends on how Bartender and the ODBC function together.  

Please sign in to leave a comment.