got_access:]
Registered User.
- Local time
- Yesterday, 20:20
- Joined
- Jun 15, 2018
- Messages
- 83
Access allows for a developer to create queries to function as record sources for forms and reports. If the developer uses this practice – he will end up with a number of queries sitting in the navigation pane which have no other purpose than to be a record source for forms/reports. In the unexpected event that one of these queries becomes compromised/deleted – its dependencies (forms or reports) no longer function.
It would seem that although this practice is an option for a developer – (and I suspect it is probably the way any number of new developers would build up a DB) – the practice appears to introduce unnecessary vulnerability.
The better practice would be to develop temporary debugged queries and load the SQL syntax into the DATA SOURCE property of the form or report, and then delete the temporary query.
I suspect professional developers address this issue?
Thanks in advance
It would seem that although this practice is an option for a developer – (and I suspect it is probably the way any number of new developers would build up a DB) – the practice appears to introduce unnecessary vulnerability.
The better practice would be to develop temporary debugged queries and load the SQL syntax into the DATA SOURCE property of the form or report, and then delete the temporary query.
I suspect professional developers address this issue?
Thanks in advance