I wrote a set of routines to allow the user to 'add another' and 'remove' FUCs as they saw fit. I also set it up so the user thought they were attaching the file to a specific field instead of the document.
I had the server administrator set the .ini parameter and everything worked great. All of a sudden, *something* broke and it was as if the server lost the .ini parm even though there was a configuration document in the NAB.
I tried getting my admin to restart the server but I guess he had other higher priority items to deal with because after a week of pestering him, I still didn't get the restart.
I'm curious as to why whatever it was broke. I suppose it could have been our installation but I'm also wondering about the stability of that parameter.
I wrote a set of routines to allow the user to 'add another' and 'remove' FUCs as they saw fit. I also set it up so the user thought they were attaching the file to a specific field instead of the document.
I had the server administrator set the .ini parameter and everything worked great. All of a sudden, *something* broke and it was as if the server lost the .ini parm even though there was a configuration document in the NAB.
I tried getting my admin to restart the server but I guess he had other higher priority items to deal with because after a week of pestering him, I still didn't get the restart.
I'm curious as to why whatever it was broke. I suppose it could have been our installation but I'm also wondering about the stability of that parameter.