You must use DAO 3.51 in A97.
Change the reference back.
Recompile.
Then try the conversion again.
After conversion, the new database will reference DAO 3.6, which is correct.
You can deselect the ADO 2.x library if you do not need it. The problem is
that the ADO library also has a Recordset object. To be doubly sure that
things are right, do a search'n'replace (Edit menu in code window) in the
new database. Replace
As Recordset
with:
As DAO.Recordset
Then compile the application to ensure everything is undersood.
For more information on references, see:
http://members.iinet.net.au/~allenbrowne/ser-38.html
For more information on converting from A97, see:
http://members.iinet.net.au/~allenbrowne/ser-48.html
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"JMCN" <picarama@yahoo.fr> wrote in message
news:2772ee20.0408120818.53306902@posting.google.c om...[color=blue]
> object invalid or no longer set - confusion of the recordset in access
> 2003.
>
> i am currently converting from access 97 to access 2003. majority of
> the codes converted over perfectly fine, though my recordset did not.
> i read from pasts posts that some references will not convert. so i
> tried to change the dao 3.51 reference to dao 3.6 in access 97. then i
> imported all of the objects into an access 2003. it did not work.
>
> so my second option was to unclick the microsoft activex data ojbects
> 2.1 library in access 2003 and left dao 3.6 object library as my
> reference. it did not work either.
>
> so am i left to just recreating the recordset in access 2003?
>
> i'm a little confused to why some of my recordsets executed without
> any runtime/compile errors.
>
> any suggestions or links that could direct me out of the dao reference
> confusion would be
> greatly appreciated :)
> thanks in advance - jung
> ------------------------
> here is the "inherited" code if anyone is curious:
>
> Public Function GetBusDays(NearDate As Date, fardate As Date) As Long
>
> Dim ExactDaysDiff As Single
> Dim TrueDaysDiff As Long
> Dim NonBusDays As Integer
> Dim LoopCount As Long
> Dim Dbe As Database
> Dim RstDays As Recordset 'rstDays - object invalid or no longer set in
> DAO 3.6
>
> 'If The Login Date is equal to Now (unlikely) or less than Now (almost
> impossible)
> If NearDate <= fardate Then
> 'then business days = 1
> GetBusDays = 1
> Exit Function
> 'If difference is less than one day...
> ElseIf Format(NearDate - fardate, "#.#######") < 1 And
> Format(NearDate, "dd") = Format(fardate, "dd") Then
> DoCmd.Beep
> 'then business days "rounds up" to 1.
> GetBusDays = 1
> Exit Function
> Else
> 'Difference must therefore be more than 1 day; calculate as
> follows...
> TrueDaysDiff = Format(NearDate - fardate, "#")
> 'Start the counter for non-business days...
> NonBusDays = 0
> Set Dbe = DBEngine(0)(0)
> 'gather the list of Bank Holidays once...
> Set RstDays = Dbe.OpenRecordset("SELECT [BH Date] From [Bank
> Holidays]")
>
> 'Loop for the gross days difference
> For LoopCount = 1 To TrueDaysDiff
> If Left(Format((fardate - 1 + LoopCount), "dddd"), 3) = "Sun"
> Or Left(Format((fardate - 1 + LoopCount), "dddd"), 3) = "Sat" Then
> 'If the above statement is true, the day is a weekend
> date: increment non-business days by one.
> NonBusDays = NonBusDays + 1
> 'The day is Mon - Fri, but it could be a holiday; check
> holiday list...
> Else
> 'always start at beginning of list for this comparison...
> RstDays.MoveFirst
> 'compare each item in the holidays list...
> Do Until RstDays.EOF
> If (fardate - 1 + LoopCount) >= RstDays![BH Date] And
> (fardate - 1 + LoopCount) < RstDays![BH Date] + 1 Then
> 'The above line takes special consideration for Login
> Dates as they have time-designations as well:
> 'The holiday date is actually the date at exactly
> 12:00 a.m. This calculation compares the looped date
> 'to the RANGE of the holiday date (from holiday date
> 12:00 a.m. to holiday date 11:59:59pm).
> 'increment non-business days by one.
> NonBusDays = NonBusDays + 1
> 'holiday date has been identified; signal end of
> loop.
> RstDays.MoveLast
> End If
> 'holiday date did not match, continue the loop...
> RstDays.MoveNext
> 'End of holiday list (SEE SPECIAL NOTE BELOW)
> Loop
> 'End determination of weekend, holiday, or neither.
> End If
> 'Move to next date within range for determination of weekend,
> holiday, or neither.
> Next
> 'RstDays.Close
> Dbe.Close
> 'Business days = gross days between now and Login Date less
> weekend dates and holidays.
> GetBusDays = TrueDaysDiff - NonBusDays + 1
> End If[/color]
