Search results

I would be tempted to expand your Data Structure a little. By all means keep your person table but I would add a table to monitor who is coming in - this will avoid you needing to contantly amending the people table tblPeople --------- EmployeeID - Autonumber EmployeeName - Text tblWorkers...

Good thanks, just been away far too long! Autonumber should make no differece as all you are hiding is the control. Sorry about the renaming lecture - one of your quirks, not renaming the ID field, surely that must say something about you ;) The other option is not a good one (and hopefully...

Couple of things Barry, Get into the habit of changing the default name that Access gives your control to something else ie Me.txtIncidentID.Visible instead of Me.IncidentID.Visible Also, Are you trying to hide a control that has the focus?

Can you explain exactly what process you are trying to accomplish.

Let Access take care of that by using an autonumber as your ID in your main table. You can then format it how you want to on the form.

Your code is grossly correct but..... Avoid spaces in field and control names as this causes a load of headaches. Also Access (unhelpully) names controls the same as the field that populated them so it can get confused on occasions! Rename your control to txtCount_Sets_1 and see if that makes...

You have to run the code in some sort of procedure so that Access knows how to run it! I have included a stand alone version but I suspect that you want to run it on the press of a button. Public Sub MergeToXL() Dim stDocName As String Dim stOrderNum As String Dim stSubject As String...

Not possible without Access in some form (full / runtime). Search the forum for similar threads as this has been asked a lot (all with the same response :cool: )

Look up the Left Function.

DoCmd.OutputTo acReport,stDocName, acFormatxls, "\\clo01\Drv F\FILEMAKER DATA\" & stSubject, True

Look at the On_Change or After_Update events of the password box.

Make sure that the form is not pop-up or Modal.

Easiest way is on opening of the database, check for the presence of the ldb file and if it exists, close down the Db. The only problem with this is if the Db does not close correctly, the ldb will remain on the drive and it will kick you out each time you open it!

Rather than running the code on your main form, create an autoexec macro and add the code calls to that (and the call to open the main form) It will then only run once on opening. There is code to screen for missing references but I have not had much joy in implementing it myself.

Yep, as I said, there are a couple of options. Refresh outlook everytime the Db is opened Refresh only if an error is encountered - not sure what the error would be though - maybe someone could help with that one. On the Form_Load event call removeoutlook() call addoutlook() and this will...

Hi, and welcome to the forum. All of your questions have been answered here befor so I suggest you use the search facility to get your answers, try these search terms for starters hide database window startup options new record form show subform Have a browse around, you will find a lot of...

Just a stab in the dark but you could try this. Public Sub RemoveOutlook() References.Remove References("Outlook") End Sub Public Sub AddOutlook() References.AddFromFile (fnFindFile("C:\Program Files", "msout*.olb")) End Sub Public Function fnFindFile(strLookIn as string, strFiletoFind as...

That Spider's web.

I have to agree with Jim. Problems with creating and deleting objects, whether dynamically or not will always create bloat (despite compact and repair) and has a strong potential for corruption! I go with jim here. How I update is to create a setup file using the excellent freeware Inno Setup...

Your idea of one alert form seems the most inviting. How about placing all of your alerts on one form but in one textbox / continuous form where they could press a button / check a tickbox to dismiss the alert. You could easily dynamically create this form using VBA and a locally held Alert...