> In response to your questions:
> "Have you tried specifying the workgroup file to use?"
> - workgroup file??
> "Do the TX users all have the same rights on the MN server?"
> - They have all of these rights on the minnesota server.
> You may also need to specify your workgroup file in your connection
> string.
> - not sure what you mean by workgroup file? Tx users are on their own
> domain seperate from Mn. But they authenticate to the Mn domain for Email.
>
> "Scott McDaniel" <scott[ at ]NoSpam_Infotrakker.com> wrote in message
> news:5vb0c2h0jfua69em1il21qjt0nsj8fg9ip[ at ]4ax.com...
>> On Thu, 20 Jul 2006 15:34:56 -0500, "Mel"
>> <Mel[ at ]REMOVE_CAPS_AND_INVALIDcircuitcheck.com.invalid> wrote:
>>
>>>on machine 'XXXX' that prevents it from being opened or locked." in a VBA
>>>application. I have had multiple users (everyone runs Windows XP) in MN
>>>connecting to an access database on the MN file server (running Windows
>>>Server 2003) for several years without and database locking issues. This
>>>week we brought on our TX facility (they are on a different domain than
>>>MN).
>>>TX users connect over the WAN to the same MN file server and the same
>>>access
>>>database as the MN users. The users in MN are receiving the error which
>>>complains about a TX user having the database locked. Any ideas how I
>>>can
>>>fix the problem?
>>>
>>>Here is what I have tried so far, with no luck:
>>>- I have checked and all users do in fact have read, modify and delete
>>>rights to the database. I even remotely connected to a TX pc and was
>>>able
>>>to create, modify and delete a file in the database directory.
>>>- Removed the database password.
>>>- Compacted and repaired the database. It compacted/repaired fine but
>>>did
>>>not fix the issue. The database is 5.71MB.
>>>
>>>Here is what my code looks like for the connection:
>>>Dim conCCI As New ADODB.Connection
>>>Set conCCI = New ADODB.Connection
>>>conCCI.Open "provider = Microsoft.Jet.OleDB.4.0 ; data source=
>>>P:\Dist\Mdb\CCI STANDARDS.MDB; Jet OLEDB; 'the error appears on
>>>this
>>>line
>>
>> Have you tried specifying the workgroup file to use? Do the TX users all
>> have the same rights on the MN server ... they
>> need read/create/update/delete on the Folder housing the db (and all
>> files created in that folder should inherit those
>> rights).
>>
>> You may also need to specify your workgroup file in your connection
>> string. Check carl prothman's page for examples:
>>
>>
http://www.carlprothman.net/Default.aspx?tabid=87#OLEDBProviderForMicrosoftJet>>
>> Note also that Access across a WAN can be pretty dicey, since Access
>> really likes a solid connection ... most LANs can
>> provide this, but WANs (even dedicated VPNs) can be quite tempermenta ...
>> I've never had good luck with it, but of
>> course YMMV.
>>>
>>>
>>>
>>
>> Scott McDaniel
>> scott[ at ]takemeout_infotrakker.com
>> www.infotrakker.com
>
>