Access 2007 & SharePoint

[Scott]

Can someone who knows about the SharePoint/Access 2007 integration
answer a question? I'm wondering what happens when an Access 2007 user
connected to a SharePoint server loses the network connection.

We have a control room that has been using an actions log that is
located on the local computer. The controllers want the db stored on
the local drive so that they can log action even if the network goes
down. We haven't been able to upgrade the db to SQL server because of
this... the controllers have to be able to update the records even if
there is no connection to a SQL server.

So, I'm wondering if the new SharePoint integration can help with
this.
If:
--The control room database was moved to SharePoint 2007 and...
--The controllers used ACCESS 2007 to keep a copy open,

Then... what would happen if the network connection failed?
-- Would the controllers be able to continue editing the database?
-- Would Access 2007 automatically reconnect when the network was
restored?

I've seen Access 2007's ability to "Take Offline" a SharePoint
database, then reconnect a copy when the user wants. The problem is
that the control room users have the database open all the time...
they would not want to take it offline then reconnect... they would
just want to keep it open, then have the Access 2007 client restore
and update the SharePoint copy automatically.

Thanks!

 

[punjab_tom]

dude if your managers are too stupid to know what they are talking
about then quit

use SQL Server; use mirroring or failover or whatever you need.
keeping your database on a fileserver is laughable, especially if it
is MDB you have to reboot the file server to clear up locks
periodically

 

[punjab_tom]

networks do not just 'go down'

I would reccomend getting a proxy server; an antivirus solution.. and
some new management

 

[Scott]

I would really appreciate a different point of view from someone
experienced with SharePoint 2007/Access 2007.

Regarding punjab_tom's response... yes, there are other ways to solve
this... but I'm looking into how SharePoint 2007/Access 2007 might
improve the situation.

To be clear for someone who can answer my question, the control room
operators keep the log database on the c: drive of the control-room
computer. They feel this is best because it is "always available,"
even in case of any kind of network issue or larger emergency. Network
interruptions are more frequent than hard-drive crashes, but the c:
drive is not backed up, so I'm not comfortable with the solution.

If you're experience with SharePoint 2007/Access 2007, can you tell me
would happen if the network connection failed?

-- Would the controllers be able to continue editing the database?
(Would Access 2007 automatically "Take All Offline," or would it
fail, like a .adp would in Access 2003?)
-- Would Access 2007 automatically reconnect when the network was
restored?

Thanks in advance!

 

[punjab_tom]

fix the root of the problem:

a) flaky managers
b) flaky networks

I had this one manager once that wouldn't let me split the MDB into a
front end and back end.

I _QUIT_

you should do the same; show some balls

 

[Scott]

"Tom"... are you so dense that you can't understand that I am working
on an option to upgrade? Granny Spitz is right about you.

I would appreciate help from someone who has worked with Access 2007/
SharePoint 2007... Please ignore "Tom" (and all his aliases).

 

[David W. Fenton]

We have a control room that has been using an actions log that is
located on the local computer. The controllers want the db stored
on the local drive so that they can log action even if the network
goes down. We haven't been able to upgrade the db to SQL server
because of this... the controllers have to be able to update the
records even if there is no connection to a SQL server.

Sounds like replication would work. Since you're already using SQL
Server you can create a local merge replica and edit that on a
regular basis. I don't know how SQL Server handles scheduling synchs
between replicas (I do lots of Jet replication but have never done
SQL Server replication), but I assume you can handle it
programmatically.

There's also the possibility to use heterogeneous replication, with
a Jet 4 MDB as a merge subscriber to a SQL Server replica set. But I
see no reason to add that level of complexity.

I wouldn't use Sharepoint as it doesn't support referential
integrity.

 

[Scott]

Thanks, David! I appreciate the input. I'll look into replication... I
haven't used that, so I'll look into it. I'll also look into the
referential integrity info... I didn't know that SP 2007 didn't offer
that.

If anyone does come up with Access 2007's behavior when it loses
connection to a SP 2007 server, I would appreciate knowing that answer
too.

 

[punjab_tom]

I SUFFERED FIRST HAND WITH ACCESS 2003 AND SHAREPOINT.

I WAS ON THE PHONE WITH MS FOR MONTHS TRYING TO GET AN ANSWER, I WAS
MERELY USING MDB IN ORDER TO PUSH 10K RECORDS INTO SHAREPOINT; ON A
LAN AGAINST A REALLY BEEFY SHAREPOINT SERVER WITH NO WORKLOAD.

IT TOOK OVER AN HOUR.

WHEN MS STARTS FIXING _CURRENT_ BUGS INSTEAD OF FIXING NEW ONES IS
WHEN I STFU

MS HAS NOT EARNED A GOOD REPUTATION FOR SHAREPOINT AND ACCESS
I AM SORRY THAT YOU ARE TOO SIMPLE MINDED TO QUESTION MS

MS ABUSES US ALL BY CONSTANT UPGRADES INSTEAD OF MOTHER FUCKING FIXING
BUGS

 

[punjab_tom]

and for the record, dipshit; you're doing EXACTLY what i first
reccomended

STFU dickhead

 

[punjab_tom]

ACCESS SHOULD BE USED AGAINST SQL NOT AGAINST SHAREPOINT


SHAREPOINT IS FOR FAGS; IT IS NOT READY FOR REAL WORLD USE

 

[David W. Fenton]

[lots of obscene shouting deleted]

Don, is that you?

 

[punjab_tom]

nope; we all know who punjab_tom is

I was working for Sound Transit.
trying to push 10k records into sharepoint through MDB and it DID NOT
WORK RELIABLY

now why is it that SharePoint is like the 'cornerstone' of 2007 when
it DID NOT WORK FOR JACK SHIT IN 2003?

MS DID NOT "EARN" THE ABILITY TO FORCE A NEW UPGRADE ON US.
FIX OLD BUGS BEFORE INTRODUCING NEW ONES!!