Gibbs said:
If the userform is not yet coded to deliver the data anywhere, the much of the work is not yet done.
As above, it would be useful to know where the data from the form needs to be told to go...
If it is excel...pretty simple...
If it is Access..little harder, but not bad..
Export to text file? not to hard either...
Not much info from what I see. I figure some of the criteria needs to be mentioned. For example if exported to Excel directory, will the Excel workbook have any chance of being opened by another user other then the one running the userform?
If exported to a text file, which is the method I used, basically the same question, will more then one user attempt to have the same text file open at the same time, including the user who is importing it? If so this can be managed but needs to be considered. In my case I keep the file to be written to as small as possible and only opened when being written to.
If there is a good likelyhood that more then one order is going to be sent close enough together to cause a conflict when the text file is open then some method should be provided to test for the opened file and make a save attempt when it again becomes available for use. Multiple text files could be used, but some method needs to be considered for naming.
When importing to Excel using my system, that text file is first copied, then the original killed if not in use and the copy is imported. Once the import is done and combined on a master sheet with all the other orders, then the whole sheet is saved to a file at frequent intervals for later initialization purposes.
By exporting to database then some if not all of these concerns go away.
So what needs to be stated is what is available, under what circumstances.
Perry
