Split database w/be on a server

[rhett7660]

Hello..

I am new to split database format... If I put the backend on say windows server 2000 or 2003 in a folder, is there anything else I need to do? Any setting on the server?? Or do I need a specific type of server os ie sql server etc?

Thanks

 

[pbaldy]

Type of server shouldn't matter. Users should have read/write permissions to the folder.

 

[Simon_MT]

Access doesn't even need to be on the Server. I would thought suggest that a decent server with at least 1GB RAM. We use a Xeon processor Windows 2003 with Raid, the later because we have so many images.

Simon

 

[rhett7660]

So there is nothing that I really need to enable etc..... Thank you!

 

[boblarson]

So there is nothing that I really need to enable etc..... Thank you!

What I would do is to make sure that your front end is linked via UNC though instead of a drive letter so anyone not using that drive letter doesn't have a problem.

See here for instructions on how to set that, if you haven't done it before:

http://www.btabdevelopment.com/main/LinkClick.aspx?link=69&tabid=55&mid=385

 

[rainman89]

What I would do is to make sure that your front end is linked via UNC though instead of a drive letter so anyone not using that drive letter doesn't have a problem.

See here for instructions on how to set that, if you haven't done it before:

http://www.btabdevelopment.com/main/LinkClick.aspx?link=69&tabid=55&mid=385

plug plug plug......

id implement boBs front end updating utility too.... saves mucho time in the long run

BTW what's brainbench? googled to no avail

 

[Simon_MT]

Bob,

What is the advantage of UNC? I once read that the Access Database should conform with the 8.3 naming convention and it should be at the top the Mapped Directory - S:/Data.mdb. Apparently this simple structure Access could undertstand and it was more efficient.

Simon

 

[boblarson]

The advantage of UNC is that a mapped drive is not neccessary and it is getting harder to find an unused mapped drive at times, depending on what software you use, or other items in use.

As far as conforming to 8.3 naming standards, I don't see that as an issue any more unless you are running Access 97 on Win 95 or WinNT4. It is totally able to handle extended file names and I've run the UNC solution at a very large healthcare company because we had to be able to use it from various locations which had the drive letters taken up and the available drive letters were not the same from group to group.

So, a single share which was accessible by anyone who needed access to the database was fine and setting the UNC links in the master kept away any problems of people accessing it.

 

[Simon_MT]

Bob,

Another tip I learnt about Servers using RAID configurations, is to create at least one small volume and one large volume. Access should always be put on one of the smaller volumes.

Many thanks

Simon

 

[rhett7660]

No mapped drives...... yet.. and thank you very much for the info... I was hoping there wasn't much more I needed to do!

 

[sjl]

The question was posed above.....

"If I put the backend on say windows server 2000 or 2003 in a folder, is there anything else I need to do? Any setting on the server??"

This was one of the answers......

Type of server shouldn't matter. Users should have read/write permissions to the folder.

Is this true....that users need to have read/write permission to the server where the backend database sits?

thanks!

 

[pbaldy]

I normally use SQL Server as a back end rather than Access, so I could be wrong. I believe the user needs write permissions to create the ldb file (and I know Access will create an ldb file on the back end when the table is opened from the front). Easy enough to test, so test it with different permissions and see if you can still edit data.

 

[Banana]

Yep, pbaldy is right. If you didn't give your users the full permission to the folder where backend is, then they will have problem, because Access doesn't run as a daemon or nonprivileged user as other server would. If this is a concern for your server, put it in a folder separate from the rest of the server, and make sure you've implemented ULS.

Another way to do it would be to use RunAs to open the database as a different user, but whether it's feasible, I do not know. (Besides, RunAs isn't as great as sudo.... )

 

[ByteMyzer]

If the server is windows server 2000 or 2003, the required End-User permissions for the back-end folder are:
* Read & Execute
* List Folder Contents
* Read
* Write

The database administrator should have the following additional permission:
* Modify

 

[Banana]

Hmm, didn't know that.

What's the difference between Modify permission and Read/Write permission?

 

[ByteMyzer]

Modify also gives a user the ability to delete a file.

See the chart below:

Special-Permissions----------|-Full-Control-|-Modify-|-Read-&-Execute-|-List-Folder-Contents(folders-only)-|-Read-|-Write
-------------------------------------------------------------------------------------------------------------------------
Traverse-Folder/Execute-File-|-x------------|-x------|-x--------------|-x----------------------------------|------|-
List-Folder/Read-Data--------|-x------------|-x------|-x--------------|-x----------------------------------|-x----|-
Read-Attributes--------------|-x------------|-x------|-x--------------|-x----------------------------------|-x----|-
Read-Extended-Attributes-----|-x------------|-x------|-x--------------|-x----------------------------------|-x----|-
Create-Files/Write-Data------|-x------------|-x------|----------------|------------------------------------|------|-x
Create-Folders/Append-Data---|-x------------|-x------|----------------|------------------------------------|------|-x
Write-Attributes-------------|-x------------|-x------|----------------|------------------------------------|------|-x
Write-Extended-Attributes----|-x------------|-x------|----------------|------------------------------------|------|-x
Delete-Subfolders-and-Files--|-x------------|--------|----------------|------------------------------------|------|-
Delete-----------------------|-x------------|-x------|----------------|------------------------------------|------|-
Read-Permissions-------------|-x------------|-x------|-x--------------|-x----------------------------------|-x----|-x
Change-Permissions-----------|-x------------|--------|----------------|------------------------------------|------|-
Take-Ownership---------------|-x------------|--------|----------------|------------------------------------|------|-
Synchronize------------------|-x------------|-x------|-x--------------|-x----------------------------------|-x----|-x