Replies

Well, considering there is no “department field”, you are going to have a problem.

Assuming there will be one, first remove any sorting. Then, select each column for sorting in the reverse order you want; that is, if you wanted to sort by “Department” and then by “Item”, you’d first sort the “Item” column and then the “Department” column.

Beyond that, you don’t have a database here; you don’t have much more than a spreadsheet. There is a litany of glaring problems immediately visible: your Food table doesn’t have a Primary Key; you defined your Quanity (I assume this was supposed to be Quantity) as a text field which eliminates doing anything like using this for totals and such; nothing is indexed; you shouldn’t be entering data directly into a table, you should be using forms for data entry; etc.

I’m assuming this is your first foray with a relational database. This is not something you can easily pick-up on your own. I’d strongly suggest you take a class to get you started-off on the right foot. Quite frankly, you aren’t likely to get much help from anyone in this or any other forum, because although many of us are here to help people with their questions, we don’t have the time to teach Access to anyone.

Just so we are clear on the situation, most of the settings being saved to the registry are user-specific. When I save them in the database, they are still user-specific. This does have the advantage in that it doesn’t matter where that user logs-in to the database, the settings are always there.

My concern isn’t about performance or “portability”. I was specifically concerned about the advisability of using these frequent updates to the registry. I guess old habits are hard to shake, so I think I’m agreeing with JoeP who said “In modern Windows registry bloat is not the concern it used to be. That said, unnecessary registry updates are just not a good idea.”

I assume you are doing this during data entry, probably in the Before Insert event of a form. Knowing nothing else about your data, start with this query (I’m assuming the fields are RecordNo, Field1, Field2):

SELECT Field2 FROM tblData Left Join (SELECT Max(RecordNo) AS MaxOfRecordNo FROM tblData) AS sq ON tblData.RecordNo=sq.MaxOfRecordData

Let’s save this as “qryLastReading”, so in the BeforeInsert Event you’d have:
Field1 = DLookup(“Field2″,”qryLastReading”)

Are you talking about upgrading the databases, or just upgrading the version of Access you are using? If the later, I don’t see any problem. If the former, your other users might not be able to use the database.

Glad to help. Good luck with it.

To run it from Access, your code would be a lot simpler, something like:

set rs=currentdb.openrecordset(“SELECT CompanyID, ZipCode FROM tblCompany WHERE ZipCode Is Not Null”,dbopendynaset)

do while rs.eof = false
varzip = split(rs!ZipCode,”,”)
For N=0 to ubound(varzip)
currentdb.execute “INSERT INTO tblCompanyZip (CompanyID, Zip) VALUES (” & rs!CompanyID & “,” & varzip(n) & “)”
Next
rs.movenext
loop

I’m curious as to why some companies are not represented in the test result. For example, I didn’t see any recent testing of Symantec products in the AV Comparative results (apparently last tested in 2010?) or VB100. TrendMicro ranked very high on AV Comparative results, but didn’t appear at all on VB100 testing.

Can we infer anything from their absence?

For a box, are you coloring the border or the background?

Here’s one example: Me.YourControlName.BorderColor=RGB(YourRedValue, YourGreenValue, YourBlueValue)

It might not help, but you can try to run JetComp to repair the database, it can be found on Microsoft website.

Were you able to import anything to the new database? What are you trying to recover? Tables, forms, code?

All form_Load does is set the rowsource of what I assume is a listbox. I’m not even sure why that is necessary, just set the rowsource of the listbox in design mode.

When do those other procedures get run?

The Watch may truncate; so in case it might, try this:

Assuming you had some existing query (maybe something like “qrySelect”), I’d do this prior to opening the recordset:

CurrentDB.QueryDefs(“qrySelect”).SQL = strSQL

If your code fails again, examine this query.

If all 4 notes records have the same value, then this seemingly would be solved by just putting a control in the header where its controlsource is that NoteDateTime field. When Access prints the header, it is looking at the first record in the group, so that’s what it will display there.

If your combobox is on your main form, requerying it is as simple as:

Forms!frmEntries!cboIDNames.Requery

Many local colleges often have “Business Education” programs that offer courses on topics like Access. Often they are held at night or on weekends; depending on how often they meet, they usually last only a few weeks, so its not like enrolling for a semester.

Thanks for stopping by to lecture us on all the things we obviously didn’t know because we only started using Access last week.