Joined: Sun 09-12-2004 8:22PM Posts: 657 Location: somewhere
Source: Kappa Sigma
Does anyone know how to set up a Microsoft Access database so that multiple people can have it open at one time? More specificly, how do I keep it from creating a .ldb file?
_________________ if you woke up as me everyday, you'd hate yourself too.
Joined: Sun 09-12-2004 8:22PM Posts: 657 Location: somewhere
Source: Kappa Sigma
Its a rush contacts database for my house.
It actually isnt a problem with the file itself, right now the problem is with some of the file permissions of the server the file is on. Apparently Red Hat doesnt like two people having a file open and writing to it at the same time. So now the question is, how do I open a file in a Red Hat samba share with read-write-execute permissions on two different computers?
_________________ if you woke up as me everyday, you'd hate yourself too.
Apparently Red Hat doesnt like two people having a file open and writing to it at the same time. So now the question is, how do I open a file in a Red Hat samba share with read-write-execute permissions on two different computers?
That's just *asking* for file corruption...and I'd suspect that you wouldn't want that on a rush database. Have you thought about what you're asking for?
You're probly better off making a simple web frontend.
Joined: Sun 09-12-2004 8:22PM Posts: 657 Location: somewhere
Source: Kappa Sigma
chip wrote:
That's just *asking* for file corruption...and I'd suspect that you wouldn't want that on a rush database. Have you thought about what you're asking for?
You're probly better off making a simple web frontend.
I'm working on a web frontend, but that takes time I dont really have right now. And the file I'm dealing with is basically the same one we've been using since at least 2000. Its just this is the first time we've had this problem because in the past we were using a windows-based server.
_________________ if you woke up as me everyday, you'd hate yourself too.
I realize you made this post like half a year ago,
but I just found it and had the answer so anyway:
Create a new blank database and import all the Tables to it. (backend)
Then create another blank database and using the Table importer, import all the otherparts, not tables. (frontend)
Then in the front end go to create new table, then link table, find the backend and link all the tables.
Create a seperate frontend for all users/ computers. You will only need one backend, but multiple frontends. If you have an Autonumber as a ID key in any of the tables add to it a computer name so you can track who makes the records. If you need any more help let me know. Also let me know if you actually read this, just for my own knowing.
Joined: Sun 09-12-2004 8:22PM Posts: 657 Location: somewhere
Source: Kappa Sigma
That seems like an awfully large amount of work to me, especially considering that I would have to make 80 some frontends when all I ended up doing was just passwording the file and dropping it on a windows box.
_________________ if you woke up as me everyday, you'd hate yourself too.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum