Re: Bugs with Quick Report Editor v18.4

2020-11-28 Thread Keith Goebel via 4D_Tech
Peter, it sounds like you’ve done an excellent sleuthing job and I’m sure 4D will want to hear about it and examine your structure to find the cause. Cheers, Keith > I've completed a bit more research into why and where the 'Error when > executing the method "db_Get_field_list"' was occurring in

Re: Bugs with Quick Report Editor v18.4

2020-11-26 Thread Peter.Burgess via 4D_Tech
I've completed a bit more research into why and where the 'Error when executing the method "db_Get_field_list"' was occurring in my database, when loading the Quick Report editor. It happens whenever the table concerned has more than one field with an automatic many-to-one relationship to another

Re: Bugs with Quick Report Editor v18.4

2020-11-05 Thread Peter.Burgess via 4D_Tech
Cheers David. Yes Windows 10. Installing XPS Viewer was going to be a last option. So thanks for confirming that it's necessary. Regards, Pete -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet

Re: Bugs with Quick Report Editor v18.4

2020-11-05 Thread Vincent de Lachaux via 4D_Tech
> There is a second bug that I've just encountered with one table, there is an > error message saying 'Error when executing the method "db_Get_field_list" at > line number 151, Indice out of range. Perhaps there is a problem with the > structure of that particular table? Hello Peter Could you

Re: Bugs with Quick Report Editor v18.4

2020-11-05 Thread David Samson via 4D_Tech
Hello Pete, I presume you are on Windows 10. Microsoft in their wisdom have removed the XPS reader and writer from Windows 10. XPS is what 4D uses for print preview. You just need to install both of these for print preview to work. HTH David Samson Manchester UK > On Windows 10 Platform, 4D

Bugs with Quick Report Editor v18.4

2020-11-03 Thread Peter.Burgess via 4D_Tech
On Windows 10 Platform, 4D v18.4. Quick Report Editor Print Preview does not come up with the current printer, instead it is looking for XPS Viewer. I don't understand why that would be. There is a second bug that I've just encountered with one table, there is an error message saying 'Error when