Hi Renee,We're having similar issues at VDL. When you select a source version that doesn't have program objects it appears that it doesn't automatically generate them for you. But instead shows the message below in the notification bar. In this instance I was able to easily regenerate the program object of this version/branch by running creation for that branch, because the named version was the last version in the branch. However, in other branches we have production databases on versions that are not the latest in the branch, and this will become a problem.For example, in the image below we have specific named version at certain points in time. We have multiple production databases running the 2023.02.01 version of the 2023.02 branch. The program object are currently available. But if they're lost I have no way of generating them again. So I would like to reiterate the question on how to generate program objects for older versions.Thanks in advance,Joey
We already use staging/temp tables for similar needs… However because of performance and security issues this is not a desired solution. I'll add the idea, as Mark suggested.
Unfortunately that won't work for us. We're looking to pass tables as parameter to procedures, in order to send larger sets of data to a procedure.Check the link I originally added to the topic, it explains it quite extensively.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
