Hi Richard,
>> Is there any reason why a PDF report cannot be displayed on a Login form?
no. A login form is like any other form. No difference there.
Of course the one thing that does spring to view is that you're using a very old NetTalk build. This makes it hard to comment on your problem, because you're using code last updated in 2015. So you're likely to waste a lot of time sooner or later encountering issues that have long since been fixed.
That said, you've got it working in the example, which is a good thing.
Perhaps your next test should be as follows;
a) create a new empty form procedure, in your program.
Add a report to that and get it working.
That will at least remove the "conflicting with LoginForm" suggestion, one way or the other.
Elsewhere you say;
>> GET /reports/$$$57653.pdf HTTP/1.1
>> I do not have a pdf in the Web folder
So it appears that the "process" is working ok. The form is expecting a PDF to be created. It should be in the \web\reports folder. It has a random name on creation, but in this case it was $$$57653.pdf
If you look in the \web\reports folder are there any files there? If there are presumably this wasn't one of them.
Aside: The $$$ in the name tells it the file can be deleted after serving. So it can only get served once.
If the file is not being created then check the settings in the _report_ carefully - both the normal report settings and the NetTalk Report Extension and compare them to the example. An incorrect setting here might result in a problem.
Also, if the report is "blank" then you might have this problem as well, so make sure the report actually has some data to display.
Cheers
Bruce