Search results

Matt, What exactly you mean when you write "create an access database" ? You can make an application that uses web pages to display and modify data. The actual data can be stored in an Access table. I don't call that an "access database" but rather a "web application that uses Access data"...

This is what you need to do: 1) Secure the back end so only the Admin group has rights. Sounds like you have done this. 2) Log in as an Admin group member and make the front end. Give members of the User group read permissions on forms, reports, etc. 3) Create queries to expose the table...

John, Try this: Dim myRset As Recordset Set myRset = Me.RecordsetClone myRset.FindFirst etc. etc I know this way works. RichM

See Access Help for "property" procedures. Basically, you define a variable in a module and then create public functions to get and put a value out or in. RichM

The basics for parameters with ADO commands: Dim pmDateFrom As New ADODB.Parameter Set pmDateFrom = ADO_Command.CreateParameter("ParamName", adDBDate, adParamInput) pmDateFrom.Value = DateFrom ADO_Command.Parameters.Append pmDateFrom HTH, RichM

Newman, In some event, probably OnCurrent, do this: If IsDate(YourTextbox) Then YourTextbox.Locked = True Else YourTextbox.Locked = False. End If I don't know what you mean about "F11". RichM

Brendan, I think this is the problem: you open a file, you write one record to the file, you close the file, you get the next records from a recordset and repeat the actions above. When you close and reopen the file, the next write replaces the previous content. So leave the file open until...

If your paths contain spaces then YOU MUST use quotes around the path. Otherwise, the example from cbragg looks OK. RichM

Mike, << DoCmd.RunSQL "UPDATE CustomerExport" & _ "SET CustomerExport.NewCustomer = TRUE" & _ "WHERE CustomerExport.NewCustomer = FALSE;" >> You need spaces between the various parts of the string. That might help. RichM

Mike, To run an "update" query, you want to use DoCmd.RunSQL(strYourSQL) instead of OpenQuery. First you build an update statement in valid SQL and assign it to "strYourSQL" which will be a string variable. Then you invoke RunSQL to perform the update. RichM

Sara, Please explain the problem some more. What do you want to see in your report ? What do you actually see ? (Examples are good) SQL is hard to follow. RichM

This is what you want to do: 1) In the MDB that contains the personnel table, remove all permissions for the group Users. Add permissions for the group Admins. 2) Open, as a member of group Admins, the MDB that "links into" the personnel table. 3) Create a query that selects the fields you...

Pssst "her" book.

This all sounds good. What do you all think of this ? Make 2 or more smallish applications with a few simple functions. Maybe: 1) a data entry/maintenence app 2) a reporting app 3) an online query app (this could be the "reference" app mentioned previously) 4) etc. I think it might be easier...

OK, that's different I guess. Multiple versions would be educational. Do you have a vision of how this thing would be administered ? RichM

Interesting idea. The "contest" part is problematic, methinks. Perhaps some kind of group effort to build a really "good" Access application instead. RichM

Yes you can use ADO on local/network Access databases. But.....most folks just use the older DAO. Go to some sites for Web developers and you will find lots of examples of ADO connection to MS Access data bases. www.4guysfromrolla.com is a good start. RichM

Sara, 1) Dim intReturn As Integer intReturn = MsgBox("Do you want to quit application ?", _ vbYesNo, "Quit ?") If (intReturn = vbYes) Then ' they chose Yes Else ' they chose No End If This is the general form of a "Yes/No" message box. "vbYesNo" is an internal constant. See Help topics...

Yes, there is a better way. See Access help for "Property" procedures. RichM

Sara << I ended up using secret option #4... let me know if this is a bad idea... but I used 2 queries on top of each other... The first was an update query which asks the user to assign a tdNumber to the current record (in tblApplicant.) The second appended to tblEmployees. This worked well...