Hi Kenneth, I’ve also implemented something similar to what others have done.
But in my case, instead of having a folder for each client, I have one folder per clientID\1000 (client ID mod 1000), so a maximum of 1000 folders. Then I have a second folder level for document classes/categories. Thus my folder structure is something like: - iDoc — P001 ——— L100 ——— L200 ——— … — P002 ——— L100 ——— L200 ——— … — … I also have the ability to use FTP to transfer files to the server, thus avoiding the need to have a shared folder. One of the reasons was that in many installations, with 100s of thousand of documents, sharing a folder on windows is very inefficient. Thus instead of requiring Clients to share a folder, the documents are sent to the server via FTP. All you need is to enable FTP Server on the 4D Server box, or i can be anywhere. In some cases we have FTP Server together with 4D Server because server also needs access to those documents. That stuff was initially developed in 4D 2004, with recent versions you could maybe transfer documents to/from server by running methods set a ‘run on server’, that do a BLOB TO DOCUMENT and DOCUMENT TO BLOB. So the documents would be transferred from/to Server by 4D. I have not tried that and thus have no idea how efficient would that be. I have not updated my code as it works fine using FTP, if it ain’t broken… hth julio > On Jan 25, 2018, at 3:39 PM, Kenneth Geiger via 4D_Tech > <[email protected]> wrote: > > Hi all, > > I’m beginning to work on a new project (4D v16 on Windows) for a client that > handles a LOT of physical documents for their clients. They’ve got a huge > storage issue and when they need to refer to a document, they spend huge > amounts of time searching the physical files. > > I’ve not started prototyping anything yet but I think I’ve got a viable > approach. The server will have a shared directory with a sub-directory for > each of their clients. There will be a dialog where the user enters > information about the document, including a text box where they can enter a > brief description of the document. The user would then drag-and-drop a scan > of the document onto the description text box and an “on drop” event would > trigger a document capture method. This method will have to rename the > document (the file-name will be created automatically within 4D without > changing the extension), check that the relevant sub-directory exists on the > server (and create it if it does not), and then save the renamed file to the > server. > > If any of you have done something similar, I would really appreciate any > feedback on my approach and would welcome any suggestions, pseudo-code, or > code that you would be willing to share. > > Thanks much, > > Ken Geiger > Dolores, CO > [email protected] -- Julio Carneiro [email protected] ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
