When I searched for the original error message I posted about, and variations on the wording, I found threads which mention that there are issues with currentdb and older access and windows versions. I think the one that actually got me to stop using currentdb in this code was on this forum...
There are known issues with currentdb and various version of access and windows. You can search all over for them. There is zero chance of me getting corporate to patch office 2007 and slime chance of an upgrade for the res tof the year....so i cant use it.
I said that I am gonna give it a...
Ill give that a shot. I am always open to suggestions (though as I mentioned using currentdb will cause me a problem).
my code is designed to not need to know how many names are on a staff list or how many fields are being audited ( currently just a provider provider list but eventually being...
This was going to be my next major step, even though I am reasonably sure it would not have solved it.
But I sort of solved it.
for the record I am running Access 2007 on Windows 7. I don't think access has ever been patched by corporate and windows 7 only has gotten security patches and...
I added
rs.close before the first and second
set rs = nothing
and
db.close
before
set db = nothing
No change.
I was using googlefu on this issue too and it looks like the .close method is something that does not do anything anymore unless your database is physically in another file...
I am the only one who even knows this database exists and if I just open it and run the macro that runs the function on the test table, this behavior occurs. It runs perfectly (except for one aspect of an if statement in terms of skipping a correction/replacement)
The SQL is literally copy...
Hello Everyone,
I am (have to) use Access 2007 to create and run a database to deal with monthly stats from one of our EMRs.
One of the things that I have to do is normalize all the different ways that the staff free text these entries in for referring provider.
So what I did was create a...
ok here's what I think is my solution, in case this helps anyone else. This may be a limitation of how I have to do things in access. And there may be a more elegant solution via VBA. But I think the following will work strictly in terms of simplicity.
My problem is that I need to create a...
sorry for not getting back sooner on this, I have like 10 or 12 differnet projects that I have to rotate between.
I did a different search and I think this is sort of what I am trying to do
http://www.access-programmers.co.uk/forums/showthread.php?t=173769
I want a chart that essentially...
the problem is that one set of data (episiotomy rates by provider) is a subset of the other set of data (episiotomy rates for all providers).
so when you use Access Report grouping feature and tie the chart data to the parent data, the group feature at the "group by provider level" filters out...
I am not sure if I phrased this correctly, but I will describe what I am trying to do, or rather being asked to do.
I know how to create a chart in an access report, put it in the group header or footer and link it such that the the grouping filters the chart.
My VP wants me to create a...
Maybe we are having a communication difficulty, which I accept responsibility for as I am still learning my way around access.
Based on some suggestions in here I have made the following query
SELECT tblTriageVisit.[Patient ID], tblTriageVisit.[PT-Name], tblTriageVisit.[pt-billnum]...
yeah, that was my original question, the actual query itself. When there was not much response I began trying to see if i could do it in the report itself.
If you go by that screen shot, none of the records for any of those procedures should be there, because they fall outside of the date for...
Each visit, in tblTriageVisits has a Admission date and a discharge date.
My idea was to use those switch statements in the text boxes to filter out those procedures that don't go with that particular patients visit. I think it sort of worked, but the one issue that happened was that even...