Hosting an Access back end as a file in a Sharepoint document library

[Isaac]

Without using Sharepoint lists or Sharepoint linked tables or anything like that, is it possible to effectively "share" and link-to, an Access back end that is hosted as a file in a Sharepoint documents library?

 

[theDBguy]

Maybe if you can "map" the document library as a network drive, but I still wouldn't recommend it.

 

[Isaac]

Yeah - that was exactly the first thing I tried, but I get this:

Just dealing with different networks and global dispersion of users and looking at options.

Thanks for the response.

 

[theDBguy]

Yeah - that was exactly the first thing I tried, but I get this:
View attachment 82974
Just dealing with different networks and global dispersion of users and looking at options.

Thanks for the response.

I think it's better to use SharePoint Lists than a document library. Otherwise, don't even use SharePoint at all. What other options are available to you? Do you have terminal services or citrix?

 

[Pat Hartman]

NO, you cannot share an Access BE this way. Only a SINGLE user can use the app at one time. If multiple users open the app, they will destroy the other person's work and I'm not sure you will get any warnings..

File sharing of an Access BE REQUIRES standard Windows protocols to manage the sharing. These are not available when you try to share a file hosted in the cloud.

 

[Isaac]

That's what I figured, hadn't ever tried it. I couldn't even get the linked table manager to allow me to select a drive letter (which I'd mapped to a SP doc library) anyway as posted in error message. Probably just as well.
@theDBguy I am not sure ... will be looking in to. We have both, not sure if they will be made available to me in this context.

I would use sharepoint lists, I've just experienced that interacting between Access and SP Lists at this stage in the game is a real pain in the behind. But then again, those were lists my manager had made with all kinds of creative field types, maybe if I use simpler field types and control the fancy stuff in the FE it will work better. Having said that, one of my main concerns is auto-redeployment of FE versions, still. Nothing quite like the luxury of a real network.
: (

 

[Pat Hartman]

SharePoint lists have limited functionality. They are not really relational tables and get bogged down with more than a few thousand rows.

 

[Isaac]

Yes, I know. That's why I hesitated to go that route. It may work for me in this limited scenario, though - until my boss figures out a way to convince his boss to cough up some budget to stand up a SQL server for our dept, my options are sadly limited.

 

[theDBguy]

Yes, I know. That's why I hesitated to go that route. It may work for me in this limited scenario, though - until my boss figures out a way to convince his boss to cough up some budget to stand up a SQL server for our dept, my options are sadly limited.

Maybe that budget is not too far away. If you have an on-premise SharePoint, it means you must also have a SQL Server already. Do you know if you're using on-premise SharePoint? Or are you using MS365?

 

[Isaac]

We're using an on-premise Sharepoint, exclusively and bureaucratically managed by the "sharepoint admin gods" of a global corporation

 

[theDBguy]

We're using an on-premise Sharepoint, exclusively and bureaucratically managed by the "sharepoint admin gods" of a global corporation

That might still be good news. Now, all you have to ask is if you or they could create a new database in the existing instance of SQL Server for your project.

 

[Isaac]

I've tried for a database before, but that's another idea - gives me an idea of who else I might ask. Will see what happens. Thanks.

 

[theDBguy]

I've tried for a database before, but that's another idea - gives me an idea of who else I might ask. Will see what happens. Thanks.

Yes, asking for a new SQL Server instance is harder. This should be easier. Good luck!

 

[The_Doc_Man]

Whenever you have the problem of getting someone to allow a new database app the problem is more easily solved if someone else higher up was asking for it. You get THAT person to advise the "I.T. gods" that their budget depends on how well they SUPPORT the company's needs, not how well they block things that they don't understand.

 

[Isaac]

Agreed ... my manager has stated he has already tried so I have to tread gently in the area.

 

[The_Doc_Man]

Ouch! Isaac, I even had Navy Intelligence types in the I.T. department because we had some servers classified as SECRET and even THEY didn't block me once the boss pointed out what they would gain and what they would lose regarding our Access database. I thought THEY were tough. But sounds like you got some I.T. guys with stones somewhere. Possibly in their head but I'm not guessing.