Jojo, this has nothing to do with a compiled app.
Besides, what I'm trying to show you has nothing to do with the "New" button and anyway it's a temporary problem *in your build*. I don't think you have to worry about having to remove the "New" button <s>.
Please do exactly what I am asking here (from the COMMAND WINDOW, it is not necessary to do it in a compiled app):
1) make sure you do not have an error handler
2) MODI REPO ?
3) when you get the dialog, pick a report of the name "untitled.frx"
I didn't say "pick the new button". I said "pick a report with the name "untitled.frx". If you don't already have a report by that name, create one before trying this experiment.
You should see the error "File In Use".
I'm trying to make sure we are doing exactly the same thing. However, the truth is, I would expect "picking the new button" to give exactly the same result -- IN YOUR BUILD.
Either way, I would expect the error "File In Use".
So I don't see how you are getting as far as the ReportBuilder.
I suspect that your error handler swallows the first (File In Use) error, and that the Designer can open initially as a result. The ReportBuilder is messed up when you try to insert your label, because the Report Designer can't create the FRX cursor that the Report Builder ordinarily works from. VPos is a field in that cursor, it's not open because the FRX isn't really available. That's because the Designer really can't open the original report form properly.
Again, this error would be gone in a more recent build. I don't think you have to worry about it.
But it's still a mystery to me how you get as far as you have gotten (the Report Designer shouldn't be opening at all) using the code that you displayed **UNLESS** your error handler is somehow involved with this.
>L<
Hi Liza,
I Got the same error you got, but why its only for the
"Untitled.frx"? Is this being used by the VFP as a template for reports? I have tried to open a different report to modify but there's no error or
"File is in used" message.
What do you think that causes this error? Any Ideas?
Thanks..
