讨论：您在哪里存储应用数据/辅助文档 [英] Discussion: Where do you store app data / secondary documents
问题描述
我想知道你们其余人使用什么文件结构来处理你的应用程序文件。
我通常拥有它以便我的前端安装到
C：\Program Files \ MyAppName \
但是我并不总觉得它是导出pdf或excel文件等适当的地方，或临时文件。
我在这件事上并没有真正保持一致，而且通常是在客户端设置安全性的问题。我有一个客户端，我无法让我的安装程序在 C：\Programs Files \ 中放置任何内容，但我可以创建自己的 C：\ My Program Files \ 然后将我的前端目录放入其中。
对于外部文件，我经常使用类似
C：\ AppNameWorkFolder \
最近我开始考虑临时文件的％AppData％\ MyAppName 和/或％temp％\ MyAppName 。另一种可能性是Documents文件夹。
我觉得我的前端存储相当鄙视，但它确实是其他的位置。文件，我觉得我没有找到最佳/最佳实践解决方案。
以我的IT锁定事物的方式。
对于Access应用程序：
客户端前端通常直接发送到％userprofile％\\\ thektop
应用程序的其余部分：
\\servername \ ... \实验室\ [部门] \ [application_name]
其中以下子项：\ backend; \rawresult; \ [等等]
当前前端位于\ [application_name]
临时原始结果文档（通常是仪器打印输出的扫描）保存在用户文档在[application_name] \ temprawresult下，直到用户批准审核然后上传到服务器。
由于IT每天运行备份，这提供了非常高的水平整个数据结构的恢复。
SQLServer有自己的备份模式和位置，因此当应用程序将其用作后端时，我唯一的区别是缺少\ backend sub。
我的家庭共享中有一个名为Access的文件夹。在那里我有一些Access项目和相当多的文件夹与Access项目。对于客户我使用他们告诉我的东西，或者我当时想出了一些东西。我通常使用项目本身的文件夹来存储相关的支持文件。有时在子文件夹中。
在我看来，你实际上已经很好地组织了笑脸; - ）
嗨其他专家，和谢谢你的回复。
我已经在伦敦度过了一个周末的假期，对延迟的后续行动感到抱歉。
我想我可能有条不紊，但并不总是尽可能保持一致。我还没找到任何圣杯。对于这个主题，也许它最终并不是那么重要。 Zmbd确实为表中的数据恢复带来了一个非常好的观点，即如果报告需要在硬件故障的情况下可以恢复，则应考虑是否存储在本地驱动器或网络驱动器上。
I was wondering what file structure do the rest of you use for your application files.
I usually have it so that my frontend gets installed into
C:\Program Files\MyAppName\
However I don''t always feel it is the appropriate place for such things as exported pdfs or excel files, or temp files.
I haven''t really been consistent in this matter, and its often a matter of how the security is set up at the client. I had one client where I couldn''t have my installer place anything in C:\Programs Files\, but I could make my own C:\My Program Files\ and then place my frontent directory into that.
For external files I have often used something like
C:\AppNameWorkFolder\
Recently I started considering %AppData%\MyAppName and/or %temp%\MyAppName for temporary files. Another possibility could be the Documents folder.
I feel rather contempt with my frontend storage, but its really the placement of "other" files where I don''t feel I have found the optimal/Best practice solution.
With the way my IT has things locked down.
For the Access applications:
The client front end is usually directly sent to %userprofile%\desktop
The rest of the application:
\\servername\...\Laboratory\[department]\[application_name]
wherein the following subs: \backend ; \rawresult ; \[etc]
the current frontend is at the \[application_name]
Temporary raw results documents (typically scans of instrumentation printouts) are held in the user documents under the [application_name]\temprawresult until they are approved by the user for review then uploaded to the server.
As IT runs backups daily, this provides a very high level of recovery for the entire data structure.
The SQLServer has its own backup schema and location thus the only difference I have when the application uses it as the backend is the lack of a \backend sub.
I have a folder in my home share called Access. Under there I have some Access projects and quite a few folders with Access projects within. For clients I use what they tell me, or I come up with something at the time. I normally use the folder of the project itself in which to store related supporting files. Sometimes in subfolders.
It seems to me you''re actually quite well organised already Smiley ;-)
Hi both fellow experts, and thank you for your replies.
I have been away for the weekend in londen, so sorry about the delayed followup.
I suppose I might be organized but not always as consistent as I could be. I haven''t really found any "holy grail" for this subject, so maybe its not all that important in the end. Zmbd does bring a very good point about data recovery to the table though, that considerations should be made about whether to store on a local drive or network drives, if it is reports that needs to be recoverable in case of hardware failures.
这篇关于讨论：您在哪里存储应用数据/辅助文档的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
