Search results

For some reason there is a problem (maybe a lag) with processing the data at runtime. It seems the best way to handle the problem was to create two invisible textboxes to store the first and last name. Then concatenate their values in a visible text box.

I know, I have an employee textbox just like it, right next to it, which works perfectly. = [EmpF] & " " & [EmpL] There are some groupings on the report, but I don't think that it would be affecting this, since [SupF] and [SupL] work fine by themselves. I just don't know what the problem...

I'd rather not use a redundant field in the query if I don't have to - and I do need the names separated for formatting. The same query is used for form filtering and the formatting of the supervisor name on the form is [SupL] & ", " & [SupF].

I was wondering if someone has had this problem before: I have a textbox on a report with the following control source, where SupF and SupL are the supervisor's first and last name respectively: ="Supervisor: " & [SupF] & " " & [SupL] What is being displayed when the report is run is...

If you would like to take another stab at this, please attach your database.

Try making a query for the export, instead of exporting directly from the table. Use the Format() function on the date field in the query.

Looks good, now we have to add "Until" and other "blue-words" to the reserved word list - just put it in the string of the other words. What we need now: - Fix minor bugs: Words such as "Database" that should not be blue in circumstances, like DAO.Database - An indent system - A table managed...

I am trying very hard to understand when there is ever a time that a Primary Key is not necessary. Every table should have some form of Primary key - whether it is autonumbered by the database, created by the user, or dynamically generated via code.

Try decompiling as Allan suggested.

MoveLast forces all records to be loaded in the recordset before the code continues. If your tables are large it could be that the system is still retrieving records from memory while the program goes on with next line of code, which can lead to unforeseen errors and incorrect data. Once the...

The fun thing about this is that there are no time constraints. Feel free to manipulate the forms, add modules, maybe even add a login feature to retrieve and post to the forum through the database.

Just wanted to start something for everyone to contribute to. Thought this would be fun. Create a code-formatter that is able to take your VBA source code and format it for color and spacing to place in the forums. I've begun by loading in the reserved words into a table, with the color...

Garethl next time, please start a new thread and reference this post in it. Your problem is that "Me" is an object that points to the current form that has focus. It is not to be passed as an identifier, but only used in VB scripting; therefore when passed as a string parameter, the function...

Manually create the table. This puts the values in the table, it does not create the table.

See Attachment. Note, I added the table and changed the return type on the function. The BLOB is being stored in two tables, which is not advised for best performance. If I were you I would reset InsertBlob to return a boolean, but modify the function to store in your STUDENTS table. I just...

You are missing the table where the blob will be stored: [tblBLOB] Fields: FKID (long Integer) FKTable (Text-255) BLOBDesc (255) FileExtn (5) BLOB (OLE Object) You call it with: InsertBLOB(rst!ST_ID, "tblDataEmployees", "Employee Pic", strFile) This function returns a boolean value that...

Next time please better format your query the post too. i.e. 'This is the code to ensure UK dates run through the fnDate function myDateEntered = fnDate(Me.txtDateEntered) myRequestReceived = fnDate(Me.txtRequestReceived) myNextActionDate = fnDate(Me.txtNextActionDate) 'Add the form details...

You never set your Table1 variable. But I think you need a little help in coding what you need accomplished. When do you want to add data to the table? When you click on the listbox, or when you double click it. Or do you just want all values in the listbox to go to the table? You should...

Make sure you do a Me.Refresh before you call the code. This forces the listboxes values to be stored. IE. Me.Refresh Table.Field = MyListBox

Note on destructor: You are both right. Access is supposed to destroy these temporary objects when the procedure ends, however Access has had issues and it is always good programming practice to manually free up memory yourself. Pat has specifically defined issues in this forum in other posts...