Search results

Made a few small changes: Row Source Type, Row Source and Bound Column properties for the list box.

People who want one million records in spreadsheets are, er, induhviduals. If it's your manager, run :D.

No, it doesn't. You can't assign to the Right() function. Try this: CreateList = Left(CreateList, Len(CreateList)-1)As for the combobox, you could try this: 1. Put the list in a table. 2. JOIN on the permissions table to populate the combobox with only those items the user has permission to...

Pointer: SELECT TOP. 1. Get the first 65000 records, ordered. Store the key for the last record. 2. Get the next 65000 records, WHERE key > KeyFromPreviousStep. Store the key for the last record. 3. GoTo 2. 4. Try to get out of previous loop. Oops.. Don't know if you can export a recordset...

For a few moments I thought it could be done in one statement. However, I couldn't do it (not saying it can't be done :p). See Module1 in attached example. Sorry about all the generic naming, but I have no idea of your context :D. I hope you don't actually have a table with that data in it...

Is the weekday in the filename, or the date?

If you want to paste multiple columns, select those columns in the table you want to paste into, then paste.

That's strange. Try to do a "Compact & Repair", that should reset the AutoNumber to use (highest ID + 1) for the next record.

Sounds like you're not actually touching the table data, just re-linking to it. Chances of corruption should be minimal. As for the copied forms etc, you'll have to test them to see if they still do the same thing they've always done. I can think of no simple way to do this.

Thanks mailman, a very good point :). You're absolutely right, the formatting should be done last. Won't help with that "LEVEL clause" error, though :mad:.

I think so. Give it a try :D.

Hey, you can always make an update query out of that if you still want to keep the totals stored. Thing is, at some point you're going to look at a wrong total if you forgot to update it. Murphy's Law dictates that the boss is going to forget to do it come next payday :D.

Indeed, nothing looks wrong. You might want to have a look at this. Makes spotting errors in big SQL statements a breeze :).

Please note that I do not endorse the use of hardcoded integers in production systems :D.

Hmm.. if I type www.google.com into a cell and click on it, it opens that web page (even without http://). It might be an Excel setting; Access doesn't seem to be the problem, anyway.

That all makes perfect sense. You may even want to consider putting all addresses in a separate table with an AddressID. That way you would need 2 relationships between the same 2 tables :D. Relationships are not a problem; they make sure that only correct and complete data is stored, which is...

I think this problem was already solved twice 5 posts ago :D

I did a quick web search for that error and found another error about the LEVEL clause, and they had to do with a ; somewhere in the sql statement. Check for that. To hunt the error down, first check the query you're basing your query on, work your way through all used queries.

Happy to help. Yell when you get to the "now I really want check boxes in my search form" bit :D. Take Singh's previous advice. Normalization might seem like overkill for such a small system, but it will pay off as soon as you add or remove a category. Besides, people will be happier to help...

Yes, it would. It would do something different, though :D. The field is a number field containing the number of seconds. Format( 93, "mm:ss" ) will yield 93 days.