Search results

probably best ignore me.. just found another thread on this issue and maybe the fact that I converted the A97 db into accdb rather than import the objects might be the issue... can't test it at the moment, will have to wait a few days Cheers, Nige

It was an A97 mdb opened in 2010 and converted to accdb, so no new features. When trying to open in 2007 it just says it's not able to open it (can't remember the exact msg and the guys 'puter that it's on isn't here ATM). 2010 dosen't seem to have any 'Save as 2007' functionality unless it...

more info required... are the strings part of the field or the entire field? if they are the whole field then a simple "update" query will select and replace if it's part of a field then selecting is easy (use 'like' in the query criteria) but replacing will be harder... maybe use 'instr'...

I'm thinking the issue you have is when you add two fields where one is a null, the answer is always null. If this is the case, read up about the NZ function

regarding the 2010->2007 scenario, are there any work-arounds? I have a 2010 accdb I'd like to open in 2007 but it doesn't want to play nice! Cheers, Nige

thanks Banana, that is great. I'm no great fan of the ribbon concept in Office but are getting used to it. For what I do, '97 was fine however the boffins that control our environment have decided it's time to move on. I have 'upgraded' my core applications to 2003 at times to use them in...

so if I'm (which I am) being forced to upgrade from '97, 2010 is the preferable option?

yes, add a command button and attach your code to it.

I'm assuming the check boxs mean something rather than that field is true/false. When I have done something similar, I used code to build a SQL statement that used the fields that had been selected. I can't find the actual code so here's some psuedo code (not correct syntax, assumes checkboxes...

no probs!!!

well to see if I could do what I suggested... (I've never used the TOP criteria before), here's a A97 db that does it using code. Have a look at the code in the Code module. The code is run using the macro 'Top 10 Pitchers'. To expand this into something useful, you'll need to take the plunge...

I don't think I read your previous question, but to me your topic 'merging tables' implies you want to merge two like tables, that article explains the complications of merging two databases with many tables. Is that what your trying to do or is it a 'simple' merge of two tables?

really simply... 1. table1: name; passport; date of joining; staff code. 2. table2: item name; price 3. table3: name; item name; quantity table3 holds who purchased what and how many.

ohh, I don't mean to do it manually... that was just non-indented pseudo code for what I'd code. It may be possible to run as macros but creating code gives you much better control.

I've used a similar concept on occasion when I want to keep those variables (for future use after the DB has been closed and restarted, maybe weeks later). They are really settings or options. So in your case, the query would be linked to this table and something to tell it the record you want...

without actually trying it... do your 1st query count how many you got (open the table, check recordcount) decide if you want more records (calculate 10-recordcount) if yes, build your 2nd SQL statement using that variable as the 'TOP' value

it might depend on what version of access you're using but in '97 you need to build up the path in a variable. Code to do it is in here someplace but here it is as I use it regularly (happen to have a db with it in it open!). CurrentDB().Name gives you the full path of the DB and you can work...

it's a very useful function... try adding two numbers when one is blank... result is nothing when 99 times out 100 you probably what it to treat that blank/null as zero... NZ will save you!

Since you don't know the filename you're going to have to determine it using code. See this thread for a way to do that. Once you have that you can then do some docmd.transferspreadsheet cmds to import each sheet where ever you want it

I think your AND needs to be an OR. This is because if the date changes, you want a new record (even if the user hasn't) or if the user changes (Date could be the same I gather). Also, add your current date assignment to make sure you've got the right date to test. If Table1!WerkDatum <>...