I have 2 form (Form1) is a log-in form, (Form2) is the Data Entry. After Authenticating the user on Form1 I used DoCmd.OpenForm "MyFormName", , , , , , varUserName, then open Form2 with following code on OnOpen event:
If Not IsNull(Me.OpenArgs) Then
Me.txtUser.Value = Me.OpenArgs
Me.Requery
Else
MsgBox ("Null")
End If
I've read about 50 posts regarding passing a value from one form to another, and I Just don't get it!
I have a table of zipcodes which I use to autofill city and state fields. The Zipcode is entered into txtCoZip. If the zipcode is in the table it autofills, but if the zipcode is not in the table, a form opens to add it to the table. OpenArgs seems to be the answer to this, but I can't quite follow it all the way through. This is the code I'm using to open the form:
Hi all, I have a form (sub_Main) that opens and has an openargs value (Department) from my main form when user clicks on a cmd button. However, if I were to go back to my main form and click on another department the openargs value is not passed along. I have tried using Me.Refresh under LostFocus but it doesnt seem to work.
What is causing the openargs value from updating? Any help?
Dim strStr1 As String strStr1 = Left(Me.OpenArgs, InStr(Me.OpenArgs, ",") - 1) Me.RecordSource = strStr1
And on the Report's On Activate Event I have
Dim strStr2 As String strStr2 = Mid(Me.OpenArgs, InStr(Me.OpenArgs, ",") + 1) Me.txtTitle = strStr2
This should work but it doesn't. The error states that the SQL statement was not found. Of course, without the second concatenated argument and Me.RecordSouce = Me.openArgs everything works fine. Can anybody see where I have gone wrong
I'm trying to make it so that an item can be returned by clicking a command button (cmdReturn) and a form (Returns) will be brought up with the ItemID field already filled in. I'm trying to use OpenArgs but am having problems. At the moment i've got
In the command button:
Private Sub cmdReturn_Click() Dim varItemID As Integer Me.Refresh varItemID = Me.txtItemID If Not IsNull(varItemID) Then DoCmd.OpenForm "Returns", , , , , , varItemID Else MsgBox "No valid item to return", , "Error" End If End Sub
And in the Open Event of the Returns form:
Private Sub Form_Open(Cancel As Integer) Dim varDCount As Integer, varOpenArgs As Integer varOpenArgs = Me.OpenArgs varDCount = DCount("ItemID", "Returns", "[ItemID]= 'varOpenArgs'") If varDCount = 1 Then DoCmd.GoToControl (Me.txtItemID) DoCmd.FindRecord varOpenArgs, , , , , acCurrent Else DoCmd.GoToRecord , , acNewRec ItemID = varOpenArgs End If End Sub
I'm getting this error message: "Run-time error '94': Invalid use of Null"
And the line in bold above is highlighted with the mouse over message saying "Me.OpenArgs=Null"
If an item already has a Return entry, I want it to go to that entry instead of making a new one. ItemID is the primary key in both tables, linked in a ONE TO ONE relationship.
Any help is appreciated, please ask questions if something's not clear. Joe
Hi I have a form with some tabs. Each tab has 2 subforms, of which the 2nd subform is always the same (call it SubformB).
I had it set up before so that the SQL query to run is passed in the openargs property to that that form and this works well.
However, on a tabbed form, each tab opens up Subform B as soon as the page is loaded. Is there a way to pass openargs to SubForm B on each of the tabs so that they all run different SQL queries even though they are essentially the same form ?
The access website says there is a way to use the open arg in combination with the FindRecord method to open a form up to a specified client name. I'm trying to have a macro that asks the user what student they are looking for and then takes them to the form with that name. The reason I can't use a query or something else is because I have macros on the form page that I want them to have access to.
So my question is this.
What's the best way to make a macro that will 1) ask the user for a name input 2) open an already made form 3) take them to a specific record based on the input name
I tried to use something with InputBox and DoCMD.OpenForm but I'm running face first into a wall any time I tried to combine the two.
Hi all, I seem to have encountered a strange problem at work.
I declared a public variable for user department. The user selects his department from a Log On form and if the password is correct, he opens another form with the department variable passed on in openargs.
All of this works fine in access2k but upon testing with 2003, the openargs somehow do not seem to be being passed on. Maybe I am being dense somewhere but it is kinda puzzling for me.
I am not using access's security for users and groups because I am trying to reduce the complexity of the whole project (I wont be around to maintain it next time).
Ok heres the situation, Ive had to edit a piece of code that worked fine filtering but wouldnt allow me to refresh a subform on the main search form. Now im using OpenArgs to pass the Selected bike ID to a popup form. This bike ID should then be used to filter the pop up form. But i get error 2001 (You cancelled the previous operation) when the code is run. The Code follows:
Private Sub cmdSell_Click()
Dim stDocName As String Dim stLinkCriteria As String
It might be an easy one but I just wasted the past hour deciphering through my code in order to solve the run-time error '94' that I'm getting when trying to execute the following code:
Code: Private Sub cmdUpdateDates_Click() '################################### 'This sub aims at combining the timesheet date and the start and end time into the fields [Start Time] and [End Time]. '################################### Dim intCounter As Integer intCounter = 0 Dim rs As ADODB.Recordset
A bit of a weird one, I've got a query and the criteria for showing records is that one particular field is null. However the query is showing records with the values in the field chosen for the Is Null.
Not sure why this is happening, has anyone come across this problem before?
I am having problems with setting up a set of combo boxes.
What I am trying to do is if combo Productline is empty then in combo PartNumber would show all products but if combo Productline has a value selected then in the combo partnumber would only be able to select the partnumbers in that productline.
Hi, I have some problem with assigmnet with date and string variable. what i wana do is get data from Forms textboxes into variable and then by insert query send to history table.
the problem occurs when there is blank textbox its says invalid use of null.
I have a query where data is first sorted by user input; first field's criteria: [fieldname], then by another field's criteria: Is Null.
I know there are records containing null values in the second field, as I have run a select query with the criteria: Like "*", to make sure they are null, and not zero-length-strings.
I have created a data base over the last few months I just kept adding information in the fields that I created but now have a problem I have the sections in a drop down menus of which access will let me ad info but when I com to save I get this message "Index or primary key cannot contain a null value"
Access will not let me save any added info in any field I have tried all the ways that I know to get round this problem to no avail it is most properly some think silly but I am desperate now as I have worked hard on this project.
I am using Access to connect to a sybase (symposium) database... I pull records depending on what state the record was pegged.... This is based apon a user inpuyting a code on a telephone. Of the user puts a number that does not reprsent any of our set codes it will show the code feild as blank or null. I need to make this blank feild something representable as furhter down my querys it removes these blanks or nulls. I would like the blank field to be shown as "Bad Code"
Any help would be great...
p.s I have used iif and as and like and nothing is working..
I would like to know if is any way to inverse the following code: This: if isnull (txt1) then 'recognise if the box is empty to something like this: if isNotNull (txt1) then 'recognise if the box is not empty
In response to: http://www.access-programmers.co.uk/forums/showthread.php?t=131593
I personally believe 'NULL' should be banned as a possibility entirely. :eek: It has been pounded into my head that 'NULL' is not the same as 'EMPTY' or 'ZERO'; and that it literally means 'NOT KNOWN'. Now consider a contact database that has a field for lets say Apt# or Street Direction such as N or S or ?? as an example. There are many, many instances where these fields would be left blank or empy: NULL | NOT KNOWN. When in fact the situation is known: the object has no such attribute; and in query or some other form of program logic the venerable NZ(subject, response) function may be used which would replace the NULL with a value. Or program logic and or error trapping would be used to handle such occasions. Which is an absurd waste of time and talent IMHO.
Therefore, if there is no applicable attribute to enter (something known) why not say so with 'N/A'? Else what we are saying by using 'NULL' is that we are building a dataset containing data that cannot be known. Kind of like saying
In response to: http://www.access-programmers.co.uk/forums/showthread.php?t=131593
I personally believe 'NULL' should be banned as a possibility entirely. :eek: It has been pounded into my head that 'NULL' is not the same as 'EMPTY' or 'ZERO'; and that it literally means 'NOT KNOWN'. Now consider a contact database that has a field for lets say Apt# or Street Direction such as N or S or ?? as an example. There are many, many instances where these fields would be left blank or empy: NULL | NOT KNOWN. When in fact the situation is known: the object has no such attribute; and in query or some other form of program logic the venerable NZ(subject, response) function may be used which would replace the NULL with a value. Or program logic and or error trapping would be used to handle such occasions. Which is an absurd waste of time and talent IMHO.
Therefore, if there is no applicable attribute to enter (something known) why not say so with 'N/A'? Else what we are saying by using 'NULL' is that we are building a dataset containing data that cannot be known. Kind of like explaining:
how do I set an entire colum to not accept nulls. example I have a colum that will be checkboxes. I want all the checkboxes to be in the unchecked state.
When filtering by form I suddenly get the words: Is Null / Is Not Null appearing in the drop down menu of all fields. I can then no longer filter at all? This is carried over to filter by form too!
When I export, or cut and paste the records into my backup database (filters working ok before I do!) the same thing happens!
