Hi All,

I have a few linked Access tables I use as lists.

I've learned that some users (by design) do not have access to the
tables, and they are presented with the username/password challenge
window.

I have not been able to predict this, and so I've resorted to adding
the following to my VBA code as a wrapper:

If DFirst("ID", "LinkedSharepointList", "ID > 0") Then
' Do what I was planning to do
End If

If the DFirst errors out, then I trap error number 3078.

Unfortunately, this is 1-3 seconds. And, because I have to do this to
7 tables, I have 20-30 seconds just seeing if the user can access the
table. And who knows if Access 2003 is gracefully opening and closing
these connections in the background.

I've tried DMax and DMin too. Same speed.

Is there a "HasSecurityClearance" function? Or a "DFast" that will do
a much quicker check?

Thanks,

Jon

SharePoint is slow as fuck.

I wouldn't reccomend using it for any reason.

If you want performance, throw away Jet and just use Access Data
Projects





On May 18, 2:14*pm, jonceramic <joncera... (AT) gmail (DOT) com> wrote:

"a a r o n . k e m p f @gmail.com [MCITP: DBA]"
<aaron.kempf (AT) gmail (DOT) com> wrote in
news:fa0accc0-295b-4510-b65e-39c2f1a432dc (AT) k3g2000prl (DOT) googlegroups.com
:

Did the Alzheimer's kick in between paragraphs 2 and 3? That is, in
the first 2 paragraphs, you seemed aware that the back end was
Sharepoint, but by the time you got to the 3rd, you seemed to have
forgotten.

Either that, or your knee jerked and your fingers just typed out
your usual boiler-plate name-calling routine.

What an idiot you are, Aaron. And you repeatedly put on display how
ignorant you are, out here for everybody to see.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

"a a r o n . k e m p f @gmail.com [MCITP: DBA]" wrote in message
news:fa0accc0-295b-4510-b65e-39c2f1a432dc (AT) k3g2000prl (DOT) googlegroups.com...

Actually, the above is not always true. In fact, if you using linked tables
to SharePoint vs SQL server, with Access 2010 those tables are local JET
tables, and you can run a report on a 50,000 record table at local non split
database speed. In this scenario Access + SharePoint runs absolute circles
around the same setup with sql server over the internet.

So, in fact, in many cases not only is this setup faster then a sql server
setup with Access, but you have full speed local processing without needing
to transfer records over the internet. This "off line" sync approach works
very well and as noted is often FAR faster then SQL server. In addition this
type of setup can handle wif or cases in which even a temp break in the
internet connection occurs.

So in fact, not only is this faster then sql server, but attempting to use
an ADP application to connect to sql server over the internet does not take
well AT ALL to small breaks in the connection. In the case of Access +
SharePoint those breaks in connection do not matter, and SharePoint is thus
not only faster for reporting, but also far more solid and reliable when
using the internet. Just in case you new to computers, there is this "new
thing" called the internet!

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

On May 22, 2:36*am, "Albert D. Kallal" <PleaseNOOOsPAMmkal... (AT) msn (DOT) com>
wrote:
Albert -

I am interested in using Access with Sharepoint for a multi user
environment. Will an Access with Sharepoint maintain data integrity?
If so, where can I find more information on the specific use of Access
with Sharepoint so I can set this up?

Steve

"SteveJ" wrote in message
news:1233347c-4c35-460b-98b6-5ceaf4adb2e8 (AT) a10g2000vbz (DOT) googlegroups.com...

One of the really great things about using access 2010 with the new edition
of office 365 or SharePoint is that you do get basic data integrity
features such as cascade delete now.

The new referential integrity features do not require access web services or
you to Publish your applications to SharePoint, but this feature also works
with just up-sizing the tables and thus keeping your application as non web.

As noted, in some cases you'll find this new setup a good deal more
forgiving and faster than using SQL server over the internet. (and in some
cases performance would be worse).
So what will work well will come down to developer experience in this
regards.

However for things like reports and select queries, these often run much
faster than using SQL server over the Internet due to the local data store
that we now have .

And as noted even better is You now do not have to go out and purchase
SharePoint, but can sign up and use office 365 now.

I do not have some great links as of yet built up (this stuff is new to
everyone, including me).

However, here are some videos:

http://blogs.office.com/b/microsoft-...ck-moffat.aspx

http://blogs.office.com/b/microsoft-...ures-demo.aspx

http://blogs.office.com/b/microsoft-...d-reports.aspx

One will keep in mind that there is still some limitations when you use
SharePoint tables for access applications. For example you don't have
compound primary keys allowed, and pretty much for the most of your designs
you want to stick to an auto number ID column for your primary keys, and
have that for all tables.

The following list limitations for access 2007 to tables on SharePoint. This
article is WRONG FOR 2010 about no RI, but it is a good outline of other
issues.

http://office.microsoft.com/en-us/ac...CH101741461033

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Pleasenospam_kallal (AT) msn (DOT) com

"Albert D. Kallal" <PleaseNOOOsPAMmkallal (AT) msn (DOT) com> wrote in
news:a23Cp.9690$4d6.5248 (AT) newsfe01 (DOT) iad:

Really? And ADP can't handle a dropped connection? That's surprising
-- is it as bad as a droped connection from an MDB connecting via
ODBC? I'd have thought that MS would have engineered ADPs to be
different, since I always thought the issue was a Jet issue.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/