Search results

I think you just answered your own question; Sounds like you are missing some code. If you post the db we can look into it.

In table design view, you will have to change the Data Type of that specific field from 'Text' to 'Yes/No' then; Optional; change the Format of that field to 'On/Off' to display the field as a checkbox in the table view itself. Also, you may want to set it's default value to True So instead of...

I think something like this might work Private Sub closeout_Click() On Error GoTo Err_closeout_Click Dim stDocName As String Dim stLinkCriteria As String stDocName = "frmcloseout" stLinkCriteria = "[clientid]=" & Me![clientid] DoCmd.OpenForm stDocName, , , stLinkCriteria...

That's pretty sick! Everyone needs to check that out!

That's basically it. The back-end only contains tables The front-end contains: Links to the back-end tables. & Everything else like queries, forms, reports etc. Yes, like you said; Most folks put the front-end directly on each user's desktop. There are other options, but I don't want...

Tell you what; If you split the database and one user's records still go missing, go ahead and remove any confidential data from the tables, and pack up the whole thing (front-ends, back-end, and each user's shortcut) into a zip file and post it.

I would still start with splitting the database; That could solve the problem by itself, not to mention it's good to do anyway. Also, it IS the 6th commandment. :p

Had to black out a little for confidentiality reasons. Basically, what I have here is a classed form docked to the left-hand side of the window at all times. Whatever the user clicks on opens the corresponding page or form on the right-hand side. The main menu options are populated by...

Without looking at your code, I can't say if it's because of the multiple users causing corrupted data, or if it's the code itself. Regardless, in your type of scenario with a database being accessed by multiple users over the network, it is a GOOD idea to split your database into a front-end...

With the code above, .MailMerge.OpenDataSource Name:=CurrentDb.Name, Connection:=strConnection, SubType:=wdMergeSubTypeWord2000 it is trying to connect the wordmerge document to the current database which, in your case, is the .mde file. I had that problem at one time and the only way to...

In the picture attached, there are two fields we're working with; Address1 and DepartmentID The picture shows two different queries that return the same results. If you wanted to run this query where; Address1 = "123 Fake St." and DepartmentID = 28 or 29 Which method would be more...

RenameField "table_name","old_column_name","new_column_name"

I believe you would copy it into a new standard module, then if you want a button to run the code, then put the following into the button's on-click event RenameField "tblRenCol","Jeff","Jeffrey"

If none of that works, you may need to change the data definition by adding a column with the column name you want, copying your original column's data to the new column, and then you could drop the original column from the table that was altered. or, use VBA...

Ok, attached is an image from the Help. This is how you run a SQL Specific query As for your particular task, I haven't had a chance to slice-and-dice this, but here is the full syntax of an ALTER TABLE or ALTER COLUMN query: ALTER TABLE table {ADD {COLUMN field type[(size)] [NOT NULL]...

I believe an update query will only update the data within a table; Here is something I found in the Access '03 Help: I think Access '03 only supports the following SQL definitions (It's probably similar for other versions too) So, unless "ALTER TABLE" works, you might be out of luck. CREATE...

Oh, I see. I misundermeant what you stood.

in Access if you have a field called "Field1" and you want the query to display it as "Field2" then in the query builder, just type "Field2: [Field1]" (without the quotes) The picture can probably explain better than I can.

Just wanted to follow up for anyone that comes across this. The latest version is working fine for a variety of PC and terminal server users here. I think some of my issues regarding speed were due to my system pulling data across the network. Since 99% of the users are terminal server users...

True that. Thanks for your help!