Why are you "starting the app" on Computer A?
Do you not have the app split into front end and back end, with the back end
(tables/relationships/data) on Computer A and a separate copy of the back
end on each user's machine?
Have you checked to see if Computer A's machine is opening in "Exclusive
Use" mode?
In any case, I suggest you separate the data (back end) from the user
interface (front end) and give each user a copy of the front end. An
overview presentation on Access in a Multiuser Environment can be downloaded
from
http://appdevissues.tripod.com/downloads.htm, and the best detail
collection of information and links on the subject that I know about is at
MVP Tony Toews' site
http://www.granite.ab.ca/accsmstr.htm.
Larry Linson
Microsoft Access MVP
"Sam Kong" <ssk@chol.net> wrote in message
news:f0667546.0310200805.7f890495@posting.google.c om...[color=blue]
> Hello!
>
> We are developing and selling an application which uses Access DB over[/color]
network.[color=blue]
> It works fine.
> However, we encountered a strange case.
>
> Computer A(DB Server): Windows 98, Access 97 (mdb), App
> Computer B(DB Client): Windows XP, App
>
> [1]
> When I start App from Computer A first, it starts fine.
> And then when I try to start App from Computer B, it gives the following[/color]
error.[color=blue]
>
> Microsoft OLE DB Provider for ODBC Drivers error '80004005'[/color]
[Microsoft][ODBC[color=blue]
> Microsoft Access 97 Driver] The Microsoft Jet database engine cannot open
> the file '(unknown)'. It is already opened exclusively by another user, or
> you need permission to view its data.
>
> [2]
> When I start App from Computer B first, it starts fine.
> And then I start App from Computer A, it starts fine, too.
> But sometimes, I can't save data on Computer A.
>
> We are using ODBC to connect to the DB.
> We developed the App with PowerBuilder 7.0.
>
> What is wrong with that?
>
> TIA.
>
> Sam[/color]
