Rowset does not support scrolling backward

[SriKumar]

Hello,

I have created a split database. The frontend interface is working fine on some systems. But on one system it shows this error: "rowset does not support scrolling backward". I am not sure why it is creating problem on only one system at this time.

I tested it on my system and on others too. Never showed any error while submitting or retrieving a record.

Please help!!!

[zmbd]

SriKumar,
You have not given us any information about the PCs, the database, what it is that you are attempting to accomplish and so forth...

Please read your post, from the viewpoint of someone that knows nothing about your organization, could you provide an answer?

[TheSmileyCoder]

I have to agree with zmbd here. First off, that doesn't sound like a error message I have ever heard before. Access usually user RECORDSETs not Rowsets. This might just be because you are translating it from a non-english language.

Are you using a normal form, with a recordsource? Are you using code? Macros?

What version of access are used on the systems? What versions of access is the frontend and backend file?

[SriKumar]

Sorry zmbd & TheSmileyCoder about half information on my problem.
Database: Access Database with tables - DB is in one of the shared folders.
Frontend UI: Access file with forms and VBA codes.
Both FE & BE are in Access 2010 version.

Code used is:

Private Sub Check_Click()
   Dim Conn As ADODB.Connection
   Dim myRecordset As ADODB.Recordset
   Dim strConn, str As String
 
    DoCmd.OpenForm "Retrieving", acNormal, "", "", acReadOnly, acNormal
    DoCmd.RepaintObject acForm, "Retrieving"
 
Set Conn = New ADODB.Connection
Set myRecordset = New ADODB.Recordset
Conn.Provider = "Microsoft.ACE.OLEDB.12.0;Jet OLEDB:Database Password=sree"
Conn.Open "Path to DB"
myRecordset.Open "Select * From [Tracker DB]", Conn, adOpenStatic, adLockOptimistic
 
SChk.SetFocus
str = SChk.Value
myRecordset.Find "[Reference Number] = " & SChk
Me.STCH.Visible = False
 
If Not myRecordset.EOF Then
    Me.Box.Visible = True
    Me.UON.Visible = True
    PON.Value = myRecordset(1)
    Me.PON.Locked = True
    Line.Value = myRecordset(2)
    Me.Line.Locked = True
    SchLine.Value = myRecordset(3)
    Me.Line.Locked = True
    PN.Value = myRecordset(4)
    Me.PN.Locked = True
    Plt.Value = myRecordset(27)
    CQ.Value = myRecordset(5)
    USDCost.Value = myRecordset(6)
    USDCFU.Value = myRecordset(7)
    Exchange.Value = myRecordset(8)
    USDTCF.Value = myRecordset(9)
    Cost.Value = myRecordset(80)
    CF.Value = myRecordset(81)
    TCF.Value = myRecordset(82)
    POD.Value = myRecordset(11)
    POCD.Value = myRecordset(12)
    SN.Value = myRecordset(13)
    Backup.Value = myRecordset(14)
    ReOp.Value = myRecordset(17)
    DisPo.Value = myRecordset(18)
    SSBOQty.Value = myRecordset(19)
    SSBOFee.Value = myRecordset(20)
    Status.Value = myRecordset(21)
    Comments.Value = myRecordset(22)
    UON.Value = myRecordset(24)
 
Else
    DoCmd.Close acForm, "Retrieving"
    Me.RefNAvaiAlert.Visible = True
    Me.AlertRef.Visible = True
    Me.AlertRef.Value = Form_PO_Cancellation_Request_Form.SChk
    Me.SChk.Value = ""
 
End If
myRecordset.Close
 
DoCmd.Close acForm, "Retrieving"
End Sub
 

Please let me know if you need more information on the issue.
Thanks much for your comments.. :)

[TheSmileyCoder]

Thanks for those updates. Much better.

A final bit of missing information from your post now is on which line the error occures.

I am going to assume the "Path to DB" is just you censoring your information. :)

I usually use DAO instead of ADODB, so I am a bit rusty on the cursors, but I thought the static cursor did support backwords scrolling, so thats odd. Also as far as I can see you only perform one navigation which would have to be forwards...

I am going to guess the error occurs on line 17, if not the following suggestions may not apply:
Try changing the recordset type, just to make sure if that makes a difference.
and / or
DAO has a FindFirst and a Findnext method, I can't recall if ADODB has the same, if it does you could try using those instead, and see if it makes a difference.

[SriKumar]

Hey TheSmileyCoder,

As you mentioned, error occurs on line 17. I tried changing to FindFirst but it says: Compile Error: Method or data member not found.

Also, I have one question... This code works on many other systems but not on one system with whom we are facing this issue. Is there any solution you can recommend there?

[TheSmileyCoder]

Hi SriKumar

The FindFirst is probably just in DAO then, and actually shouldn't matter as you explain its working on other systems.

Do each user have their own frontend on their own PC or do they share a frontend file on a network share?

If they have their own frontend file, try giving user a new frontend file (You probably allready have, but if haven't try it)

Other then that I can only give general vague advice really. Make sure that both you and the user in question has the same version of Access installed (including service packs). Make sure the user has all updates. Do you both use the same operating system version?

Does the user have the same rights as you (or other users) to the folder in which the backend resides?

Check that the user has the same version(s) of all referenced library's in the vba project.

Other then that....good luck

[SriKumar]

Hi TheSmileyCoder,

Thanks much for quick response...
I will check all the points with that user and let you know on the outcome.

[SriKumar]

Hi TheSmileyCoder,

I have checked all the points with the user.

1. Do each user have their own frontend on their own PC or do they share a frontend file on a network share?
   
   - Yes, user has his own file on this desktop.
   
2. If they have their own frontend file, try giving user a new frontend file (You probably allready have, but if haven't try it)
   
   - tried this one too.
   
3. Other then that I can only give general vague advice really. Make sure that both you and the user in question has the same version of Access installed (including service packs). Make sure the user has all updates. Do you both use the same operating system version?
   
   - We both have same Access Version. But I developed this DB in WIN7 system and user have xp.
   
4. Does the user have the same rights as you (or other users) to the folder in which the backend resides?
   
   - We both have change permission to the folder.
   
5. Check that the user has the same version(s) of all referenced library's in the vba project.
   
   - Library references are matching.

Now I am stuck badly ... :(

[TheSmileyCoder]

Im quite sorry to hear that. I really have little else to offer at this point.

Your other users do they also use Win XP or is this the only user who uses Win XP? (To be honest I don't think this is related, but I have nothing better to suggest)

Make sure that the user has a fully updated system. If nothing else helps, try to get him to reinstall access if possible.