Search results

First thing I notice is you didn't specify relational integrity for all your relations. I took a quick look in your atached database and noticed you use table level lookups, 8 reasons not to use them. To me it's not clear what purpose this database has, I can see it has something to do with...

Some region settings require the use of a semicolon ";" in stead of a comma.

Yes it can be done if the table structure for your tables is the same you can use a union query. the easiest way to make one is building the query for one month in the QBE grid the switch to SQL view add Union to the end and add the next month. Why are you storing your data in separate tables?

Your problem is that VBA works with dates in the US format, leave the format option or use the US format. Note: The variable mydate is not declared if you set option explicit at the top of your module you should have declared it (as date).

It can have something to do with the "[ ]" arround the SQL string and in VBA you can't use the query syntax of refering to a field on a form. I think it should be something like this (I added linefeeds because I think it's easier to read) : Set rs = CurrentDb.OpenRecordset("SELECT...

What do you want to do with it? My sample gives only output to the debugging window of the VBA editor as yours does now. What is the table structure you want to enter the data? To enter it in a table you can use a recordset or a append query which you can build in the function. If YourTable has...

Try the split function, for your example it would look something like Dim yourstring As String Dim i As Integer Dim StringtoParse As Variant yourstring = "PROJECT1 GROUP1-25%, GROUP2-50%, GROUP3-25%." StringtoParse = Split(yourstring, " ") For i = 1 To UBound(StringtoParse) Debug.Print...

"=" means the same, to use wildcards you need "like", so in your case it should be: like "cashpayer*"

If you use Dim userID as integer you get this error because you assign a null value to something that can't be null. You should have used Dim userID as variant Edit: Moniker was faster and I do like his solution.

Although it may not be the case here you should be explicit in what kind of recordset you want (DAO or ADODB) Dim db As DAO.Database Dim rst As DAO.Recordset

The only limit you have is the size of the database (max 2Gb for AC2000) so I don't see any problem there. Default Import from Excel in Access will look for the data type in the first row (or the second if the first is column headers). If your sample info is correct I don't see the point in...

Maybe you can use this ldb viewer.

1) I have no clue what you wan't to do here it may be that the dlookup function can help you but it cauld be easier to copy the record and alter the date. 2) If you make your select query grouped you can do the math there. 3) You could join the Extra work with one of the other fields in the...

Rabbie is right, if it has to be upper case. To check or filter on non uppercase you need the strcomp function like: StrComp([YourFieldName];UCase([YourFieldName]);0) Make this the source of a new colum in a query and every result that's not 0 is not completely in upper case.

I made a sample database so you can see how to do things. I used your Exelsheet as a header but didn't take the time to covert it to access so some colums will be out of line. Hope this helps.

You can use the KeyDown event for that, something like Private Sub YourControlName_KeyDown(KeyCode As Integer, Shift As Integer) KeyCode = KeyCode + 2 End Sub You will need some kind of check for results after the Z.

I'm glad you decided to redesign your table structure, to get the desired layout you need a Crosstab query (the wizard can help you with that). To make a comment on your structure: I hope you didn't put spaces in your Table names as they can make things difficult in the future and I strongly...

Posting the SQL of your query would make it easier to see why you have problems finding the blanks. If you use a like statement to filter your records you miss any empty fields (you are searching for a string and the field contains nothing, the "is null" would work for these). Some...

If you normalize your tables you don't need a union table. To enter data you can use a form for the project with subform to enter hours, if you make this a continuous form the number of employees on a form is endless.

Your tables are not normalized and it will be a hell of a job to get reliable data from it. You said you have only worked for two weeks on this database so in my opinion your best solution would be to read up on a normalized database (do a search here) and change your database accordingly. For...