by Jeffrey D. Lanc » Thu, 06 May 1999 04:00:00
Greetings,
Has anyone had problems with .AddNew not adding a record when MS Access
has the Database open? I thought if the Table was open, then MAYBE it
might limit the ability of VB to write to it somehow but as it turns
out, if the MDB file is open with access at all then the .AddNew command
is ignored.
Jeff
by Jeffrey D. Lanc » Thu, 06 May 1999 04:00:00
I solved my own problem although I don't understand why it made the
difference fully:
I had the field I was creating a new record in as an indexed field no
duplicates. When I changed it to nonindexed, it works fine.
> Has anyone had problems with .AddNew not adding a record when MS
> Access has the Database open? I thought if the Table was open, then
> MAYBE it might limit the ability of VB to write to it somehow but as
> it turns out, if the MDB file is open with access at all then the
> .AddNew command is ignored.
> Jeff
1. Busy Day = Slowdown from 12 AM - 5 AM
The only thought that I have:
* Are you perform your daily backups during this time?
* Was there a program modification recently done?
* Do you have nested subroutines?
Just thoughts...
Grant
2. SQL 7.0: Simple one. Using "NOW()-x dayes" when creating a view
3. I am getting this message when i am tring to export or import anything using
4. Problem with Insert statement
6. The invitation to cooperation in IT branch
7. error ORA-01855: AM/A.M. or PM/P.M. required
10. I am having problems with addnew
11. New line break - ( I am new to the world of sql server)
12. Multi-User DAO/JET AddNew doesn't work? Am I missing something?