Your AutoID is immaterial to what you are doing.
Why do you need to start from zero? If, for some reason you do, then you have to just use a regular number format and populate it yourself.
You have to open Excel and check each sheet or at least one if it contains data - if it does you proceed with the TransferSpreadsheet, otherwise you stop.
Popultaing the ComboBox in Excel is not an issue. Another question - is Excel used as a data entry tool or a calculation engine?
Why not design the app in Access and export the data into Excel (maybe as a pivot table)?
Will users be updating Access from Excel? In that case the two-way traffic...
What is the point of working like Word if it is for data entry. It might always be exported to Word and formatted accordingly through Word VBA...
Enter Key behavior should be enough.
Svet
I think you might want to look into ASP for what you would like to do and maybe some scripting. My suggestion was for Access. If you create the table and execute the query it will do exactly what you are describing.
Svet
Little note on previous setup, it might be a bit slower than running IF or SELECT but you don't have to go and change VBA code when rates or limits change, all you have to do is make changes to table, you can even create a nice form to update table from.
Svet
I would set up the following table:
ID CL_Def Limit Rate
01 Class1 0 1.250
02 Class1 500000 1.500
03 Class2 0 0.750
04 Class2 250000 0.850
05 Class2 350000...
In each app I always have a main form called frmMain.
frmMain has lblStatus in navy backcolor, white forecolor.
I put the code below in a module named Status.
Then I have:
Public Sub Dummy()
Status.StatusBar "Please, wait. Importing..."
Call Import
Status.StatusBar...
I found an answer- by opening another Access and taking the Systems tables with the specs to the back-end my front-end does not bloat.
Not the most elegant way, but since I import 16,000 records I thought speed would be an issue so I used the Transfer method.
Svet
I generally avoid using the Transfer methods but for the purpose of speeding things up I decided to set up File Specs and use the TransferText method of a front and back end Access 97 application.
Turns out that the front-end size bloats when I use this method, apparently it has something to do...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.