@scottalanmiller let's assume that we get direct application access from Word/Writer into SP or NC, how do you send a link to someone else so they know they have access? How do you register that 'link' in some way so that the correct application launches when trying to open the link?
How do you do it today? Why would it need to change at all?
Paying particular attention to Gene's wording, there would be no more files, only data in a DB. In that case, to send the information via email would mean extracting that data into some kind of usable format then emailing it.
So the contents of the file are simply sent as a file.... that's all a file normally is, a database holding text directly on it with a label on it with the filename. So.... literally nothing changes here under the hood. There is no more or less extraction than before.
You were weren't talking about getting rid of docx files and xlsx files, etc?
Yup, and still am. No files, but that doesn't mean that you can't have a file "view".
But OneDrive, etc still store those things as objects, I don't think you can edit the 'Word.doc' file directly inside the DB, you need to send that object of data to Word to edit it.
As objects, not as files. I don't need to pull the files from OneDrive to edit them. I can talk to the database directly with MS Office 2013 or later, even the online version.
Yeah Office is a bad example because of the massive integration.
Or a good example because it shows how easily it can be done and how well people can't even tell.
LOL - yeah, but you are limited to only MS based files, All other files are just stored as objects in the DB.
Are they? I'm not sure of that. But that's always going to be the case. File systems are for ad hoc, unplanned files. The real question should be... why do such files exist in your environment? When do you actually want ad hoc file types that you didn't expect?
Actually Sharepoint does not natively interface .doc files either. It only uses the new format .docx files in the manner you are saying.
Don't I know it.. I was playing with SharePoint and damn if I didn't have all kinds of problems with DOC files.
And... you'd need a database to track the databases!
Actually, as I think about it, separating databases really just becomes semantics. As long as it is a single application, separating the databases adds overhead (mostly for the developers) but in reality, it is always still all one datastore. One way or another, the application has to behave essentially the same no matter which way you do it.
The one advantage to having them separate is that you can have different "versions" for different customers. But I'm not sure that that is a good thing.