Please help an old X-baser who’s out-of-touch !
In Dbase/DBMAN/KMAN we used to be able to save variables to disk inside the database. This allowed me to start the application with the record pointer at the same position on subsequent runs.
Short of writing to a text file outside the DB, I haven’t found a way to do this in Access 2000.
Have many apps where I filter data based on selected month/year. Would like to open DB with the same M/Y still selected. I’d have thought this to be a common request and addressed neatly within Access (like a tie-in to the MonthView ActiveX control that recalls last state), but I can’t find any examples in the Help system or KB. I’m hope I’m just using the wrong logic or terminology.
Someone suggested everything should be in tables, so I currently use a single-record table called “CurrentStuff” to hold selected month/year. This doesn’t seem the most efficient answer, and creates a problem in Queries if the date info isn’t broken-out into separate fields in the main table (if I use calc or SQL to equate fields I can’t update table via query) as in the SQL example below where I try to relate a month [CurrentStuff.CurrentMonth] to the month of a full date [DatePart("m",[Extended]] :
This works as expected, but doesn't allow edits.
Sorry to be so long-winded.
Any thoughts would be much appreciated.
In Dbase/DBMAN/KMAN we used to be able to save variables to disk inside the database. This allowed me to start the application with the record pointer at the same position on subsequent runs.
Short of writing to a text file outside the DB, I haven’t found a way to do this in Access 2000.
Have many apps where I filter data based on selected month/year. Would like to open DB with the same M/Y still selected. I’d have thought this to be a common request and addressed neatly within Access (like a tie-in to the MonthView ActiveX control that recalls last state), but I can’t find any examples in the Help system or KB. I’m hope I’m just using the wrong logic or terminology.
Someone suggested everything should be in tables, so I currently use a single-record table called “CurrentStuff” to hold selected month/year. This doesn’t seem the most efficient answer, and creates a problem in Queries if the date info isn’t broken-out into separate fields in the main table (if I use calc or SQL to equate fields I can’t update table via query) as in the SQL example below where I try to relate a month [CurrentStuff.CurrentMonth] to the month of a full date [DatePart("m",[Extended]] :
Code:
SELECT Tasks.[Client Name], Tasks.Description, Tasks.[Month Due], Tasks.[Day Due], Tasks.Extended, Tasks.OutDate, Tasks.Partner, Tasks.[In-Charge], Tasks.Remarks
FROM Tasks INNER JOIN CurrentStuff ON Tasks.[Month Due] = CurrentStuff.CurrentMonth OR ((DatePart("m",[Extended]))=CurrentStuff.CurrentMonth)
ORDER BY Tasks.[Client Name], Tasks.[Month Due], Tasks.[Day Due];
Sorry to be so long-winded.
Any thoughts would be much appreciated.