Search results

access 10 and possibly access 07 lets you do it. back when i posted i didn't have access 10 ETA just reread the thread and remember what this was for. this was for an access 03 database for an office that doesn't want to go to office 07

hi gemma/David)))) no, it's not completely new but there will always a situation when they just entered a new record on the main form and the 1st nested subform will have no records. i'm just trying to prevent the situation of them adding the 2nd nested subform records before they add the 1st...

can anyone help please?

Yes, I was able to. I mentioned oracle when you suggested referential integrity - that I can't do with oracle. So about the dlookup, I'm probably stalling, but what would I be searching for? Can you do it in my example?

I can't enable referential integrity, these tables are linked from oracle. So there's no way to know in vba that the parent form has no records? That's my problem, that even when there's no parent record - clicking ADD still creates a child record.

Hi, how do i make sure that parent form has a current record? i have no problem doing it as long as the parentform has ALLOWADDITIONS enabled, but in my case it's disabled and i tried every trigger i can think of - and if there's no records in the parent - the user can still click the ADD...

Thank you so much for all your answers and patience

here's where i'm confused and why i didn't think of doing this. what i thought might happen is that my function keeps on going but then a minute later, another one somewhere in the back starts going too. so i didn't think i would see it in the present running code. so are you saying that in...

perfect. but what do you mean? what will debug.print show me? won't it just display all the queries? you're saying to put Debug.print in front of each query? or what?

running 40-50 queries that update QuickBooks tables. i mean only 5-10 actually update the tables, the rest get the data ready.

hi, i did try researching this but probably didn't google the right words. what happens if the form timer event is set to every minute, then it fires, procedure runs and it takes 5 minutes. do the next 4 times get skipped or what happens? thank you

Gemma, i really needed you over the weekend: i had 1001 questions)))))))))) but that's ok, i got more lined up)))))))))) as far as the warnings - i just posted what i think is happening: they turn themselves on once i make some kind of changes to the forms and/or vba. i haven't figured exactlt...

i figured it out. they turn themselves back on when i go into design of forms and make changes in the vba behind it. and i ended up not using db.execute because it didn't work anyway.

i know that it bloats it but i don't like having another database. i compact on close so i should be ok. these are small anyway. as far as turning off warnings - i don't want users to see any messages at all. i think i wrote code that stops them all but in case i didn't - i don't want them to...

i use setwarnings on opening of the database and never turn it back on. i want it to stay permanently off. i don't know if it's a coincidence but since i moved the BE to SQL server - the warnings turn back on after using some forms. i'm getting the "are you sure you want to replace the table"...

ok, in case anyone is interested. since then a few errors got logged and i think i understand what's happening. the errors i was talking about were sql errors like: this record can't be deleted because the FK_blah_blah is .... like straight up sql errors. and it seems like those don't get...

oops, you're right. i got so caught up in the fact that this is an error logging program that i didn't think to look up the error that i'm getting. but i can't get it to come up now, i fixed everything i noticed and don't remember exactly what made it come up. anyhow, i will google the error...

i'm still checking but so far i'm getting the same results i was getting earlier with my own search. most of the posts that i get deal with the fact that once you switch to the SQL BE - the code throws an error that it "you must use dbSeeChanges". i'm already past that point, i've fixed that...

1. there is no error, that's my problem. it doesn't log ANY errors. 2. thank you, will check now.

Hi, another (3rd so far) problem when something worked with an Access BE and doesn't with an SQL BE. i was using Allen Browne's LogError procedure to log all errors to a table so i can review and fix them. once i switched to an SQL BE - the errors don't get logged. every single error goes to...