Re: DoCmd.GotoRecord in Access97 vs. Access 2000

From: Laurie Brand (laurie_brand_at_dom.com)
Date: 03/10/04 

Date: 10 Mar 2004 08:02:37 -0800

Hi, Billy.

Thanks again for the ideas.

> As to the Error 2105: Can't go to the specified record, I think the Jet version
> is not related with this issue. To isolate this possible cause, you can copy
> the DLL files from 2000 machine to your NT machine and register the DLL
> files one by one.

Which files? I don't see any .dlls related to jet in the System32
folder?

>
> Based on my view, if the problem persists after putting the "Order By"
> statement (original in queries) in the Form_Open event as below:
>
> ''''''''''''''''''''''''''''''''''''
> Private Sub Form_Open(Cancel As Integer)
> Me.OrderBy = "Field DESC/ASC" 'Modify it as you please
> Me.OrderByOn = True
> End Sub
> ''''''''''''''''''''''''''''''''''''

The Order by is in the Open event.

> We may consider the following things:
>
> 1. Check the Data tab on the Forms Properties ***.
> If the "Allow Additions" property is set to false, it might cause this problem.

Allow Additions is being programmatically set to true when the user
clicks on the "Add New Record" button that is built on the form. I've
tried remarking out that code and setting it permanently to true, but
it doesn't change anything.

> 2. If your Form's RecordSource is a Query or an SQL String combining 2 or
> more Tables, check and make sure that the Query / SQL returns an
> updateable Recordset.

The forms recordsource is a single table and it is updatable when I am
in it or when the other user is in it, independently. Only when we
both go in does it lock the other one out.

> If the Query / SQL String returns a non-updateable Recordset, you or your
> user cannot modify existing Records or adding new Records. You can
> open the Query by itself and see if an empty row (for a new record) button is
> shown. You can also check whether the NewRec button in the
> NavigationBar is enabled or not. If there is no empty row (NewRec button
> disabled), your Query is not updateable and NewRec is not allowed and
> therefore, on your Form, you cannot go to NewRec.
>
> 3. Whether or not there is no PK for the queried table

Yes, there is a PK on the bound table.

> If it exists, please check if there are any indeterminate relationships between
> your tables. It is recommended that you define a primary key for the
> queried table if it has not one.

There is only one table in the recordsource with a single field PK.
There are no relationships built-in through Access in this
application. The relationships designed between the tables are
maintained through code, but the Access tools are not used to define
these relationships.

>
> 4. Are you able to go to a new record using the navigation buttons?
> If you and your user both can, I suspect the problem might be located in the
> VBA code. If that, could you help post it to reproduce your issue?

Yes, I can go to a new record if I'm in it alone. If the Access2000
user opens the application, then I cannot go to a new record. As soon
as he exits, I can again go to a new record.

Billy, thanks again. I'm out of ideas, but appreciate any other
thoughts you might have. I don't believe any of this is programmatic.
 Is there another news group that I could post to that might be better
in resolving a network/jet/software incompatability issue?

Laurie