 |
|||||
|
As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Join the TIBCO Community
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community. | |||||
Read-Only TopicGo | Search | Notify | Tools |
| WINFORMS file not created | Login/Join |
| Virtuoso |
Hi all, I'm currently busying myself with building some fairly simple maintains. I'm now using 764 for that, and something strange happens in 764, at least it happens in my VM image. Never seen it before. The issue is, that after creating the maintain with it's screens and logic, I wanted to run it by right-clicking the procedure and click on Run Procedure. The thing got analysed and such and after closing that small window it tried to run the maintain. But all I got was the message that it could not find the winforms file for my maintain. I toyed around a bit with all kinds of attempts to get this file created, and I only got it to work to create a new deployment scenario, deploy it (to another app of courtse), then copy the wfm file from that other app to my initial app folder. As of that point the maintain is runnable, maintain updates my wfm file and I'm happy again. .... Until the next new maintain. The same thing starts all over again. Does anyone one why in heaven this wfm file does not get created for a newly created maintain? GamP
| ||||||||
| |||||||||
| Master |
When you are in the MDE, does the little white box up top say "Local Deploy." If not, change it. If so, then it could be a permissions error. I am not sure if this is your issue, but try the following: -Go to explore/tools/folder options/view tab and uncheck "use simple file sharing(recommended)" -Click on apply and ok. -Right click on IBI folder and add IUSR_machine_name with full control. Mark | |||
|
| Virtuoso |
Alas, it's not a permissions issue. And yes, the box says Local Deploy. This strange behaviour seems to happen only when I create the maintain from within the MDE environemnt, I did not have DevStudio actvie at that time. Somewhat later I did have DS active and created a new maintain from witin DS, which started MDE todo the development, and I did not have any problem with that maintain. So I think I'll just keep doing it the DS way, in stead of only the MDE way. Thanks for reacting. GamP
| |||||||||
| ||||||||||
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only Topic | View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |