Access violation error while configuring report button

Hello Sparrow,
The DTP_Time_VISIT field is saving correctly to table AA_002_REC_Visits, field Time_Visit. Something may be wrong with  Report(SQL) script.... I don't know.
Regards,
Eyeman

your project modif

Hi Eyeman,
As Sparrow has already reported, the access violation error was due to you trying to associate a 'time' field with a 'calendar' object - logically, calendars are associated with 'date' fields, not 'time' fields.
With regard to the report(sql) script, I had a very quick look and there are a number of errors (there may be others, I didn't go through the whole script)..
1.  On lines 6 and 29 you are calling calculated fields (age and cf_staffman).  Calculated fields don't actually exist at the database level, they are just temporary calculations when the program runs so cannot be directly referenced as part of an sql statement..
2.  On line 7, there is a space imbedded in the field 'name_ of_doctor;  MVD accepts this but as an sql statement, it will almost certainly produce an error.
3.  On line 50, you have left a comma after the last selected field (impression).
These can be easily corrected.  However, the bigger issue is your 'where clause' which has inner joins to 67 tables!  I question what sort of response times you'll experience with such a query - if it works at all (but as you know from previous posts, I have reservations about the number of tables and forms that you're using generally). 
Is there really data in all 67 tables that relate to the initial record that you want to report on?  You could always use 'left outer join' instead but again, it's the number of joins that concerns me.
With regard to 'good practice' (and I'm sure everyone has different ideas so it's just a personal opinion), I would suggest that you 'start small' with such a query -  include just a couple of tables and, if it's working, then build it up gradually and testing as you go along.  Writing it all at once and then finding out that it doesn't work is a bit of a waste of time and makes trying to debug it extremely difficult.
Derek.

Hello Eyeman,
I have had another quick look and there are still a number of syntax errors in your report(sql) script - I haven't been through it all but a couple are:
1.  you are still referencing calculated fields (cf_staffname)
2.  missing commas between selected fields (field 'os')
3.  references to tables and fields that don't seem to exist (table L010?)
4.  fields selected twice
5.  fields ambiguously defined (for example, the field 'notes' is referenced in both aa_030 and aa_057).
However, trying to correct the above errors (and possibly more that I haven't bothered checking) is, in my opinion, a bit of a waste of time and effort. 
Having now seen the .pdf that you included in your attachment detailing how you want the information to appear, I believe what is needed is a main report (the patient's OPD visit) with a number of subreports (with each subreport corresponding to your .pdf sections of clinical symptoms, medical history, visual acquity, glass power etc etc).
I don't use FastReport very much but I imagine that would be quite a complicated report to produce.
Instead of the main report / subreports approach, a much simpler alternative might be to write a number of discrete reports (one for the 'OPD visit', one for the associated 'clinical symptoms', one for the associated 'medical history' etc etc) and then chain them together (in other words, you run the first report and when it finishes, it automatically calls the next one etc etc);  this has 2 major advantages:
1.  you could probably write them using 'report' (rather than 'report(sql) which would also get round the calculated fields problem).
2.  you could run a specific report, if required, rather than the whole 'suite'.
I can't see any other practical way of achieving what you want although there may be other Forum members who can think of a different approach.
Derek.

Hi,
Have a look at the attached example.
In it, you can run each of the 3 reports separately or use the 'chain'.  The 'chain' is simply a bit of script that calls each of the reports in turn.
If you need a 1 page summary report, it depends on what information you want to give to the patient;  just try not to end up recreating the same problem that you had when using report(sql).
As a 'rule of thumb', if you can display the summary information in a tablegrid, then you can pass it through to the report (in essence, your tablegrid becomes the dataset that is used by FastReport).
Derek.

Hello,
I was trying to create a small report (AA_Form_007_OPD_VISIT_REC.Button13) displaying the glass power of the patient. However, on preview, the data is not displayed. Ditto for Summary Report  (AA_Form_007_OPD_VISIT_REC.Button1). Where is it going wrong?
Regards,
Eyeman.

Hello Sparrow,
Thank you for the guidance. I changed to Left join for these tables, but still no data. Perhaps other Inner Joins override the Left Joins. I changed all to Left Join and now the data appears in Preview of FastReport. However, all data from child tables are displayed and not for the desired A002.id. How to solve this issue? Need AND clause? Left Join may be ideal, as often the child tables may have a null value.

Hello Sparrow,
Thank you for the response. I am indebted to you and all the learned Forum members and Derek, in particular for guiding me at every step in my projects. Definitely, I will read more about JOINs. The Report needs to display the data entered in all the child tables for an OPD_ID on a particular date. The A002.id is unique for each OPD_ID and date, and id_A002 is a foreign key in all the child tables. This query is getting additional data for A002.id  referring to a different OPD_ID and date. Why is this happening?
Regards,
Eyeman.

Try to fix your request like this.
Add last line "AND ..."
Hope this solves your problem)

...
where
A002.id = $id
AND A006B.id_LU_010_Eye_Select=A006.id_LU_010_Eye_Select

You are welcome

I will repeat again. )))  I recommend reading help about JOINs in SQL.
This AND ... part of the JOIN. Your two tables A006B and A006 have a common id_LU_010_Eye_Select.