Change Field name in Table with VBA
Thank you for taking the time to report an issue.
What's wrong... Please write below.
I can't seem to get it to work in either VBA or as an expression. In VBA I get a debugging error as to how I reference the table field value. In an expression (I am not sure how to refer to the back color of a field) I first tested with true returning "Good" and false returning "Bad".
Even though the table field value is blank, it returns "Bad". I even tried to include IsNull(""), but this still returns "Bad".
Even if I put a value in the table field and refer to that in the expression, it still returns "Bad" instead of "Good".
At the moment I don't have a date selection form before the report, but I have a record in the table that shows when switching the report to View mode.
The lookfield upc should only be able to except the values greater then 10 but less than 100. Do I come up with a validation rule for this field in this table? If so what is it? Or is a form with vba the way to goand if so what is the vba
The reason for these gymnastics is that I am selling some software that will integrate with ShipRite and I need this to happen programitically so I don't have to physically go to each client to do the install.
I have a table with a field name "distcode." I need to change it simply to all caps; DISTCODE. In Design Mode I type DISTCODE, save, and when I view the table the field name is all caps. But when I close the database and reopen the table the field name is back to all small letters. What is forcing this default change?
The Data Type is Text, and this table is not linked to another table
I need to put the last hour of the day and employee for the field EndTime.
It is possible for vba cod?
Look at the picture in attached, please.
In this article
* What happens when I change the field size?
* Change the field size of a number field
* Change the field size of a text field
This is fine for all the simple tasks, but what I have myself into is a little more complex than the Macro builder is ready tohandle I think.
Before, when I created a button, not a Macro. I am trying to build the following button types:
Button 1 - Update a Field in a table, Save form, Close form
Button 2 - Update a field in a table, save form, new record
Button 3 - Update a field in a table, save form, print report, close form . and so on and so forth.
I used to put 3 or 4 buttons on the form, then copy and paste the generated vba in the correct order in a single button, and delete the dummy buttons. But now it seems as the basicfunctions are built using an embedded macro, and when that is combined with VBA, Access must choose between one or the other, rendering my button useless.
Is there a setting in 2010 that will change the way buttons are created in that VBA is used by default instead of macros?
I can easily see a method if one can put vba in the front-end form that the user uses. I can use vba to insert a change code into that record's log field.
But I can not see any method that would exist only in the back-end file. Is there any technique out there?