I simply want to run a report for the current record that displays and/or prints only the logical fields = Yes. God I miss dbase...
views:
63answers:
2
A:
You can do this a couple of different ways
- You can base the report off of a query that lists only the records you want to see:
select * from foo where bar = true; - You can base the report off of a table and then add filters to the report to get the exact rows you want. The filter is basically the where clause.
As for dBASE, blame Ashton-Tate for screwing up the schedule on dBASE IV 1.1 for that.
CodeSlave
2009-09-09 17:34:58
Why would anyone miss xBase? It didn't support SQL!
David-W-Fenton
2009-09-09 20:25:24
Hey, I didn't say that I missed it; I'm just empathising with the original poster.
CodeSlave
2009-09-09 20:35:08
Thanks CodeSlave!!! I knew there was a simple answer, it's just that I havent needed to create a database app since dbase and early versions of Foxpro that acccepted dbase commands in a "command" window. For the record, and as a sad indication of my age, SQL didn't exist when I last had to create a dbase app. Thanks again...
2009-09-09 21:11:15
@David W. Fenton: "xBase? It didn't support SQL!" -- Access database engine SQL only bears a passing resemblance to actual SQL :(
onedaywhen
2009-09-10 12:11:42
@onedaywhen - I use Access and SQL Server and don't see the huge discrepancy as far as the SQL commands go.
Jeff O
2009-09-10 13:28:35
@GuinnessFan - I think that was said (mostly) in jest. There are some discrepancies between Access's implementation of SQL and ANSI-SQL. Some things would be so much easier if it was ANSI compliant.
CodeSlave
2009-09-10 14:06:29
No jest from me: Access database engine SQL is nothing like the real thing: UPDATE syntax, DISTINCTROW, FIRST/LAST set functions, etc are more than mere 'discrepancies'.
onedaywhen
2009-09-14 12:45:55
A:
- Go to Insert->Report
- Pick your Table/Query of interest, then go to the Design view.
- Drag 'n drop your fields of interest.
PowerUser
2009-09-09 20:38:14