Subcomponent:|none
Assigned to:|msc
Reported by:|macuser_winpgmr
--- Additional comments from [EMAIL PROTECTED] Sun May 15 14:50:47 -0700
2005 ---
In Base, after running a report, the resulting new report document has several
problems when saved to various
y:|P3
Subcomponent:|none
Assigned to:|msc
Reported by:|macuser_winpgmr
--- Additional comments from [EMAIL PROTECTED] Sun May 15 14:45:34 -0700
2005 ---
In Access, it's common to run a query interactively or via Automation, then use
Select All a
y:|P3
Subcomponent:|none
Assigned to:|msc
Reported by:|macuser_winpgmr
--- Additional comments from [EMAIL PROTECTED] Thu May 12 13:05:10 -0700
2005 ---
Queries don't support the calling of macro functions. In Access, a query field
expression can referen
bcomponent:|none
Assigned to:|msc
Reported by:|macuser_winpgmr
--- Additional comments from [EMAIL PROTECTED] Thu May 12 12:55:25 -0700
2005 ---
In Base 1.19.100, once a view has been designed it can't be changed.
Not really sure what the point of a
y:|P3
Subcomponent:|none
Assigned to:|msc
Reported by:|macuser_winpgmr
--- Additional comments from [EMAIL PROTECTED] Thu May 12 12:52:26 -0700
2005 ---
In Base 1.9.100, tables placed in reports have to be big enough to handle the
worst case number of re