All hail VB! Yep, I'm a worshipper of VB as compared to Macros. Since my first Access database, if it's got to do something, I want to do it with nicely commented VB. I used to have to (in Previous JobTM) periodically work out where an uncommented database which relied heavily upon uncommented macros (and vanishing temporary tables) was producing anomalous reports such as the delivery of 32.5 BMWs to a customer1.
I think that she's using linked tables. From what you've said, that would explain the daily corruptions. And as for the freelance Access dev, you might just have sold your soul, my son ... [grin]
I passed on your suggestions, but She Who Will Not Be Mentioned is slightly narked that no-one told her there could be a problem with SQL, and she was in fact told that it would be more stable using SQL as back-end. I did mention that Microsoft would be unlikely to want to mention that two of their applications didn't play nicely together.
1 My initial suggestion that it might have been a convertible was appreciated by my manager, but not passed on to the customer.
no subject
I think that she's using linked tables. From what you've said, that would explain the daily corruptions. And as for the freelance Access dev, you might just have sold your soul, my son ... [grin]
I passed on your suggestions, but She Who Will Not Be Mentioned is slightly narked that no-one told her there could be a problem with SQL, and she was in fact told that it would be more stable using SQL as back-end. I did mention that Microsoft would be unlikely to want to mention that two of their applications didn't play nicely together.
1 My initial suggestion that it might have been a convertible was appreciated by my manager, but not passed on to the customer.