Can someone help fininsh a VBA / Excel database

pontiac

Board Regular
Joined
Jan 7, 2003
Messages
64
Alot of the front end work is done, The userform is to the point of just writing some VBA to shift the data entered on the userform to the database.
There is a reward for this help. I have to have this fininshed before the first of 2006..

Please someone help..
 

Some videos you may like

Excel Facts

Which Excel functions can ignore hidden rows?
The SUBTOTAL and AGGREGATE functions ignore hidden rows. AGGREGATE can also exclude error cells and more.

pfarmer

Well-known Member
Joined
Jul 6, 2005
Messages
550
pontiac said:
Alot of the front end work is done, The userform is to the point of just writing some VBA to shift the data entered on the userform to the database.
There is a reward for this help. I have to have this fininshed before the first of 2006..

Please someone help..

What do you mean by Excel database.

If you simply want to import the contents of the userform to a different Excel workbook, then one method is to save the contents of the userform to a text file, then import the text file.

There are other ways, such as writing to the other workbook itself, but each can have various drawbacks.

Or do you mean sending the contents of the userform to a database such as Access, etc.?

Perry
 

XLGibbs

Well-known Member
Joined
Feb 25, 2005
Messages
2,446
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...
 

pfarmer

Well-known Member
Joined
Jul 6, 2005
Messages
550
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
 

Watch MrExcel Video

Forum statistics

Threads
1,118,069
Messages
5,570,010
Members
412,304
Latest member
citrus
Top