Search results

I have an issue with a database layout and I am not sure which is the best way to proceed. The problem is in an invoice part of a db . When a service is delivered, say 2 hours of a technicians time, it has to be assigned to a particular tech. No problem when there is only one tech however...

Not quite sure what RSnEW(0) is but if it is a string variable of some sort then syntax should be similar to =""" & RSnEW(0) & """" . If it is a recordset then I dont believe that you can include it in the SQL string. DISTRICT has to = a string of somesort which of course could be an individual...

Checkout the following thread http://www.access-programmers.co.uk/forums/showthread.php?t=79038

An alternative approach is to trap "error 3021 No current record" and use this to add a new record to the recordset.

Rob I would suggest that you would need to create a new form that was based on a recordset created using the input from the combo box. There are a number of ways of doing this check round this site and others for examples which could then be put into the afterupdate event for the combo box. I...

Before running the Docmd.runsql insert Docmd.Setwarnings False You should then insert Docmd.Setwarnings True after your proceedure.

The correct syntax is either where [ fieldname ] = " & """ & criteria & """" or where [ fieldname ] = " & " ' " & criteria & " ' "

Ron Presuming that qInd_info is the query that does the filtering that is the likely source of the problem . Bit difficult to advise without seeing that query. Perhaps the filtered query is returning no results which would mean that the recordset would be empty therfore no emails!

james I dont believe that you have your SQL grammer quite right try either "[Delivery_SigRef] = " & " ' " & Me!Delivery_SigRef & " ' " or "[Delivery_SigRef] = " & """ & Me!Delivery_SigRef & """"

I think you are missing brackets and quotation marks in the WHERE definition examples as follows SELECT TblIssuetypes.[Issue number] FROM TblIssuetypes WHERE (((TblIssuetypes.[Issue number])="9")); SQLstatement = "SELECT TblIssuetypes.[Issue name], TblIssuetypes.[Issue number] FROM...

I've struggled with this particular problem for a little while and I think I have cracked it as follows In the OnLoad or OnOpen procedure in the subform DoCmd.GoToRecord , , acNewRec In the main form in the OnCurrent procedure for the main form Me![subFormName].SetFocus...

@ Jon K Thanks any idea why , I have not had this problem when opening recordsets based on SQL strings before

With a bit of search through the forum ( perhaps I should have done it before I put the post up!) I have found a solution but really dont understand why. If SQLstatement = "SELECT TblIssues.Issues, TblIssues.[record number] FROM TblIssues WHERE (((TblIssues.[record...

I have a little problem that is driving me crazy although I am sure the answers simple I run the following code SQLstatement = "SELECT TblIssues.Issues, TblIssues.[record number] FROM TblIssues WHERE (((TblIssues.[record number])=[Forms]![frmEnterIssues]![txtRecordNumber]));" Set db1 =...

@ spacepro the fields on the main form are locked as the form is designed to enter data on the subform the data on the the main form is for info only however as a test I did hit the add new record button on the main form and the subform does indeed go to a new record @ liv tried this but no...

There's probably an obvious answer to this but I can't spot it. I have a form with a sub form the data in the sub form is from a table at the many end of a one to many relationship with the table upon which the main form is based. When the form opens I want the sub form to go to a new record...

Roy I have pretty much given up on including the issues in the db not because of the yes/no issue which is a fairly minor programming issue but because of the more general difficulties. Basically the db is to include details of approx 500 individuals part of this ideally would be be basically a...

Roy Unfortunately the issues involved will only be defined once the database has started being used and yes this will cause all sorts of headaches. The issues could be collected as a series of notes but this would make analysing them impossible. I may drop this bit altogether

I want to add a column to an existing table using the sql statement Alter table. The new column needs to be a yes/no type. The following code almost works but it only sets the column to a general logical type not specifically the yes/no check box . DoCmd.RunSQL "Alter Table TblIssues Add [" &...