Search results

OK... Haven't used "Shell" before so.... little fit of dumbness here :) I have 2 textboxes you fill via command buttons.... The photo program "ProgramPath" and one to the image.." ImagePath" The shell like this Private Sub CmdCall_Click() Call Shell("""[ProgramPath]""[imagepath]", vbNormalFocus)...

What a siimple little code..... :) Thanks Paul... Is this the correct syntax? Works fine...opens window viewer. Where would I insert the .exe of another photo program if I wanted to set up a choice? Private Sub CommandFollow_Click() Dim strPath As String strPath = Me.imagepath...

I want to do something with a photo DB, but not sure how to make it work.....OK, we've all seen alot of the different, really nice DB's people have done for photos on here...using the path to the folder where the photo resides. Mines set up that way... Basically set up so I can have a memo...

Do a search on field validation.... You'll find a lot. If you run your own code, your message box will come up first.

"People involved" is a little vague :) Are these multiple people who will have the same "Classification"? For example... 5 or 6 different people working at one location.... You might have 6 or 8 at your second location? If so you could do this with a subform or a linked form... Use datasheet or...

A code I like to use for data validation is below. This is set for the BeforeUpdate event .... But could be changed to a function and called from the onclick event of your button.... OR just put on the OnClick event of your button.... Depends on how you want it to act... Private Sub...

Well, after opening the DB, it makes little sense to me.... Maybe someone else can take a shot at this... BUT... A couple things first....again.... Normalize the database. Look at the relationships... With this sentence...... "I have a table [WHEELS] with a list of wheels. There I included too...

I'll open it when I get home. But no matter what version you use the table structure is still incorrect. You have duplicate fields.

I can't open your DB at the moment, don't have 2007 on this computer.... But, First thing I see is your table structure. WHEELS (ID, PN, SN, OH_CYCLE) OH_CONTROL (ID, PN, OH_CYCLE, ACTION, CONDITION) First, I would not use spaces....they get you into trouble. tblWheels (WheelsID, PN, SN...

Sounds like your checkbox is unbound. In most cases a checkbox should have a field in your table with the value of "Yes/No".

You might find it easier to change the "Limit to list" property of the combo box to "No"

Did you actually copy the DB? Or did you import one DB forms and tables and queries into a new blank DB? If you did the import you can choose to import with or without data.... Sounds like you did the later...

I saw this post and was going to ask if you were moving between versions....03 to 07.... But I see you said you had an attachment field so I assume only 07... I had this same problem on a project.... But I don't think I ever figured it out. I think on mine the reports were being corrupted when I...

Not sure exactly what you are referring to... but look up "Find Duplicates Query Wizard" in Access or check this page..... http://office.microsoft.com/en-us/access/HA010345581033.aspx?pid=CL100570041033

I think it might be easier to look at your table relationships. Under "Edit Relationship" (By right clicking on the line joining the tables) make sure "cascade update related fields" and "cascade delete related records" are checked..... if both apply to your app.

Use the visible property.. An "if ....then" statement or a "Select Case"... For an example, this is one for an option group... "Yes or No" to display a textbox for the date if the option is "Yes" Private Sub Hired_Click() Select Case Me.Hired Case Is = -1 Me.HireDate.Visible = True Case Is = 0...

I think the "Easy way" for alternate Row colors is Access 2007 :D

First, its seems rather odd to be putting these two together..... Your clearing all the text, combo, list and checkboxes..... then running code to execute a message box if they are null.... Of course they are going to be null, you just cleared them. So for this to ever get past the message box...

For Each ctl In frm.Controls Your running different code on the exact same thing...... Why do you need different tags? Call it "c" or "v" or whatever...... or use a "not isnull"

If you place a "c" and a "v" in the tag of course this code is going to be ignored... Your tag is "cv" not "c" or "v"........ My first question for the code is...... why? Your clearing textboxes, combos, whatever... that then will obviously return the error message when the second code runs. Use...