Search results for query: *

You usually get this message with A97 when attempting to open a DB created with A2K or higher. Uncle Jack

Usually this kind of information is contained in a single table. See for example, the customer table wizard. Doing so would eliminate the problem you're currently experiencing. Uncle Jack

Access can handle 4-5 concurrent users, but it can be slow on occasions. Put 10 on it and it really bogs down. It's kind of like those cars that are billed as five passenger. Yes, you can put five people in them provided they're all children or midgets. You can use Access with 150 users...

Rick has put it about as eloquently as I've ever seen. You need to read about "Normalization" before designing your tables, and I stress the plural. It would be extremely rare for any table to have several dozen fields in it. Think in terms of compartmentalization for easy of...

Because of the problems outlined by Rick you might be better off NOT to use autonumber, but use program assigned numbers instead. Most people don't use autonumber fields for real data, but only as line counters where the values are really irrelevant anyway. If you choose to use program...

Create a form and place combo boxes for parameter choices and text boxes for date parameters. For example, use a combo box named "PickManager" that queries the table for managers. The user simple selects the manager of choice. Other fields would be handled in the same way. User...

I don't know about your specific situation, but I've used SendObject in runtime A97 without problem. So I don't think it's the SendObject command per se that's the problem, or at least not the whole problem. In fact, here's the exact line of code I used: DoCmd.SendObject acSendReport...

I don't think you can do it with a query since I can't think of a way to limit a query's scope to just three lines. However, you might be able to do it by using DAO. The following should read in three locations from the input line number and place the concatenated value in a different field of...

If the users have direct access to the backend then the only way is to implement user level security making sure that the backend is also secured. Otherwise anyone with a retail copy of Access and enough brains to open a database can pirate your data structure. Uncle Jack

You can use an input box in the OnOpen event of your form to collect a password. Then test the password to see if it's correct. If it isn't then close the form. This isn't a perfect solution which would be as jpa suggests, implemention of user level security, but either approach has problems...

In the AfterUpdate event of your text box, place this code: If Me!Textboxname = 0 or IsNull(Me!Textbox) then Msgbox "Enter a value greater than zero dummy!" Me!Textbox.Setfocus Me!Textbox.bordercolor = 255 else Me!Textbox.bordercolor = 0 end if :) Uncle Jack

Depends on what records you want to combine and a host of other variables that you didn't specify. Generally you can concatenate records by simply joining them thusly: [Field1] & " " & [Field2] The square brackets tell Access to take the contents of the field enclosed in brackets...

Depends on the type and format of information you want to insert. If you can display the information in table format either as a table or as the result of a query, just highlight the columns and rows of the table, copy to the clipboard (Ctl + c) and paste (Ctrl + v) into the Word document. OLE...

I need to read the first four bits of a byte. Anyone know a way using VBA to do this? Uncle Jack

It's best to have the static data in each front end. That way each station doesn't have to use the network to fill combo boxes to select school grades, states, or other stuff that isn't going to change. Conversion to MDE just compiles all the code in the DB and isn't impacted by the location...

This time it worked. Have fun. Uncle Jack

I'll be happy to send you the code. However, the EMail address you supplied did not work. Uncle Jack

Static values can be either a value list or a query based on a table. I don't think it really makes any difference. Obviously, if you get above 10 or 12 choices or if the static values are subject to periodic change, then you should use a table based query. If you're splitting your database...

Hi Terry: How about setting the record source for form 2 to a named string variable, like "MyString"? Have form 1 set the contents of the MyString so it's available when form 2 loads. That way the record source for form 2 always has the same name, but different values set by form 1...

Use the follow or follow hyperlink method. A third alternative is to use Shell. Uncle Jack