Subject: RE: R601 CF2: BUG! Special database object cannot be located
exactly the right place. The published workaround helped me to resolve the problem quickly. Beside, Issue still persistent in R602 CF1 (Windows 2000 sp4)
Subject: RE: Workaround for: R601 CF2: BUG! Special database object cannot be located
Hey Bo,
Thanks a lot for the posting. It really answered a few questions we had here at Coloplast as well :o)
Does anybody know is this is indeed a bug (ie. classified by the developers) or is it an undocumented feature? If it is a bug, does anybody is they plan to fix this? Soon? :o)
Subject: RE: Workaround for: R601 CF2: BUG! Special database object cannot be located
Thank you soooo much for posting this. We just upgraded to R6 on Friday and surprise surprise we couldn’t access our forms on Monday. Great to be able to stop in here and get an answer so quickly.
Subject: Another solution for special database object cannot be located
I also had the same problem on R601 CF1. I checked my $SubForms fields in the document properties and it did not show any subforms at all. But this post and another one referring to an “unknown server” led me to delete a special Javascript subform that was on the original form. This subform was coding to allow a web reporting service record hits to my database documents. I deleted the subform and I could immediately open the form.
Since I really want that subform on the form, I deleted the subform, did the changes that I needed to do to the form and then pasted the subform back in. Without doing anything on the form to add the subform back in, it still is there and the application seems to be working properly from the client and from the web.