SBS 2008 + Multi User Microsoft Access DB

Hello everyone

I'm having an issue hosting a multi-user access db from SBS 2008. I
has the same behavior Windows Vista did prior to sp1

Problem
One user opens database, other user tries to open database, it hang
while loading the database. As soon as user one closes the database, i
opens right up for user 2. The lock is being held exclusively to th
first user. Hosting an access database on Vista behaved this exact sam
way until Sp1. I am wondering if there is a workaround for server 2008

The share is setup with everyone as co-owner on the share/db. The onl
solution prior to microsofts update last time, was to host the data on
fat32 partition so the ntfs permissions didn't come into play

Anybody having this issue? I thought it was a thing of the past now. :

Any help or suggestions are appreciated, thanks for reading

-Lei

--
MSLeif

In article <>,
says...
> I'm having an issue hosting a multi-user access db from SBS 2008. It
> has the same behavior Windows Vista did prior to sp1.
>
> Problem:
> One user opens database, other user tries to open database, it hangs
> while loading the database. As soon as user one closes the database, it
> opens right up for user 2. The lock is being held exclusively to the
> first user. Hosting an access database on Vista behaved this exact same
> way until Sp1. I am wondering if there is a workaround for server 2008.
>
> The share is setup with everyone as co-owner on the share/db. The only
> solution prior to microsofts update last time, was to host the data on a
> fat32 partition so the ntfs permissions didn't come into play.
>
> Anybody having this issue? I thought it was a thing of the past now.
>
> Any help or suggestions are appreciated, thanks for reading!
>

Microsoft Access is a DESKTOP database, not a real database. Since you
have SBS 2008, download, if you don't already have it, one of the free
versions of MS SQL and install it - convert the Access DB to MS SQL and
use MS SQL, your problems will be gone.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)

Leythos wrote:
> In article <>,
> says...
>> I'm having an issue hosting a multi-user access db from SBS 2008. It
>> has the same behavior Windows Vista did prior to sp1.
>>
>> Problem:
>> One user opens database, other user tries to open database, it hangs
>> while loading the database. As soon as user one closes the database, it
>> opens right up for user 2. The lock is being held exclusively to the
>> first user. Hosting an access database on Vista behaved this exact same
>> way until Sp1. I am wondering if there is a workaround for server 2008.
>>
>> The share is setup with everyone as co-owner on the share/db. The only
>> solution prior to microsofts update last time, was to host the data on a
>> fat32 partition so the ntfs permissions didn't come into play.
>>
>> Anybody having this issue? I thought it was a thing of the past now.
>>
>> Any help or suggestions are appreciated, thanks for reading!
>>
>
> Microsoft Access is a DESKTOP database, not a real database. Since you
> have SBS 2008, download, if you don't already have it, one of the free
> versions of MS SQL and install it - convert the Access DB to MS SQL and
> use MS SQL, your problems will be gone.
>
And with all due respect sometimes that Access is a LOB app and you
can't. It may be a DESKTOP database but tell THAT to my vendors.

Permissions on mine are Everyone, full access.

Access 2000 and it works fine.

Open up the permissions more.

I'll try - they seemed as open as they could be. I might just need to
take another look.


--
MSLeif

In article <u#>,
says...
> And with all due respect sometimes that Access is a LOB app and you
> can't. It may be a DESKTOP database but tell THAT to my vendors.
>

Being a production DBA for many years I can honestly say that I've been
there many times, stupid vendors that can't seem to comprehend that MS
has provided a FREE MS SQL version for more than a DECADE and that it's
infinitely more stable and usable/sharable MS Access ever way.

There are SOOOOOO many problems with MS Access, just the added
support/trouble costs alone can provide the ROI for a small SQL
instance.

--
You can't trust your best friends, your five senses, only the little
voice inside you that most civilians don't even hear -- Listen to that.
Trust yourself.
(remove 999 for proper email address)

I agree that SQL Server is a better multi-user solution than Access, but
there's no reason Access shouldn't work well on a LAN with a modest number
of users. Check that the first user is NOT opening the db in exclusive mode.
This sounds more like an Access issue than a file share issue. Access
databases worked fine shared from a Vista workstation too, as far as I
remmeber, but there were networking issues pre-SP1 that impacted
performance.

Check that workstations have current network drivers, and if possible in
your environment, exclude .mdb files from real-time virus checking. Each
user should have a local copy of the front-end db with all the forms, code,
etc. and linked tables running from their own disk drive. Only the data
tables should be in the shared backend db on the server. If your db is not
yet split into a front-end and back-end, then you need to split it as
described or you will have multiuser problems including likely data
corruption.

Finally, you should post in an MS Access newsgroup since this seems more
likely to be an Access issue than an SBS issue.

"Leythos" <> wrote in message
news: om...
> In article <>,
> says...
>> I'm having an issue hosting a multi-user access db from SBS 2008. It
>> has the same behavior Windows Vista did prior to sp1.
>>
>> Problem:
>> One user opens database, other user tries to open database, it hangs
>> while loading the database. As soon as user one closes the database, it
>> opens right up for user 2. The lock is being held exclusively to the
>> first user. Hosting an access database on Vista behaved this exact same
>> way until Sp1. I am wondering if there is a workaround for server 2008.
>>
>> The share is setup with everyone as co-owner on the share/db. The only
>> solution prior to microsofts update last time, was to host the data on a
>> fat32 partition so the ntfs permissions didn't come into play.
>>
>> Anybody having this issue? I thought it was a thing of the past now.
>>
>> Any help or suggestions are appreciated, thanks for reading!
>>
>
> Microsoft Access is a DESKTOP database, not a real database. Since you
> have SBS 2008, download, if you don't already have it, one of the free
> versions of MS SQL and install it - convert the Access DB to MS SQL and
> use MS SQL, your problems will be gone.

"MSLeif" <> wrote in message
news:...
>
> Hello everyone,
>
> I'm having an issue hosting a multi-user access db from SBS 2008. It
> has the same behavior Windows Vista did prior to sp1.
>
> Problem:
> One user opens database, other user tries to open database, it hangs
> while loading the database. As soon as user one closes the database, it
> opens right up for user 2. The lock is being held exclusively to the
> first user. Hosting an access database on Vista behaved this exact same
> way until Sp1. I am wondering if there is a workaround for server 2008.
>
> The share is setup with everyone as co-owner on the share/db. The only
> solution prior to microsofts update last time, was to host the data on a
> fat32 partition so the ntfs permissions didn't come into play.
>
> Anybody having this issue? I thought it was a thing of the past now.
>
> Any help or suggestions are appreciated, thanks for reading!
>
> -Leif
>
>
> --
> MSLeif


FWIW, I've seen this issue with an installaton. When they moved the Access
database to an XP machine from the 2008 SBS, it worked fine. After a little
research, it was determined it was an SMB difference with the newer
operating systems. The admin disabled SMB v2 on SBS 2008 that was sharing
the Access Database, and it seemed to do the trick.

Read up on it, and see if this applies to your scenario.

How to Disable SMB 2.0 on Windows Vista/2008Server Message Blocks Protocol
(SMB) is the file sharing protocol used by default on Windows-based
computers. SMB 1.0 was designed for early Windows ...
http://www.petri.co.il/how-to-disabl...erver-2008.htm

Ask the Performance Team : Two Minute Drill: Overview of SMB 2.0May 30, 2008
.... Finally, to disable SMB 2.0 on Windows Vista or Windows Server 2008
systems that are acting as the “server”, navigate to the registry key ...
http://blogs.technet.com/askperf/arc...f-smb-2-0.aspx

How to Disable SMB 2.0 on Windows Vista/2008Aug 4, 2008 ... In this article
Daniel Petri will talk about another one of the "advanced" networking
features of Windows Server 2008 and Vista - SMB 2.0 ...
http://digg.com/microsoft/How_to_Dis...ows_Vista_2008


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA
2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer

For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.

Susan Bradley wrote:
> Leythos wrote:
>>
>> Microsoft Access is a DESKTOP database, not a real database. Since you
>> have SBS 2008, download, if you don't already have it, one of the free
>> versions of MS SQL and install it - convert the Access DB to MS SQL
>> and use MS SQL, your problems will be gone.
>>
> And with all due respect sometimes that Access is a LOB app and you
> can't. It may be a DESKTOP database but tell THAT to my vendors.
>

Access isn't bad as an entry-level rapid application development system,
and is obviously optimised for database use. It's conceptually easier to
deal with than Visual Studio or similar, and Access does prevent some of
the classic database schoolboy errors. Quite a lot can be achieved
without writing a line of code.

And while a multi-user LOB application doesn't actually have to be split
between a user interface .mdb file, containing forms, reports etc., and
a database .mdb file, this is the customary way to do things for a
number of reasons. No Access professional would consider producing even
a small and simple database application using a single file.

There's no problem at all in replacing the back-end .mdb file with a
connection to an SQL database, or indeed any other data source that can
talk ODBC. Doing so removes the largest risk with networked Access, that
of the fragile data file being corrupted by a disconnection. It also
speeds things up considerably, as the entire table or joined tables do
not have to be copied across the network when a query is run. All of the
investment in the schema and user interface design is retained, and the
raw data also becomes available to other ODBC front ends.

--
Joe