not in list problem

[Guest]

that's the way that i started the application but it didn't work when i start
using the openrecordset commands in the code, the only way that i was able to
make it work was with the connection object.

 

[Brendan Reynolds]

Well, without seeing the code that was not working, I can not say why it
didn't work! All I can say is that this method does work, and is the
usual and standard way of doing these things in Access. I'm afraid it sounds
like you read the wrong book. While I can understand your reluctance to
change tack now, there is an old saying that when you find yourself in a
deep hole, the first thing to do is to stop digging.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[Guest]

ok, thank you for your advice i'll give it a try to your suggestion and see
what happens.

 

[Dirk Goldgar]

sorry for the confusion but i'm new on this stuff i've alway use
access just as a reporting front end, this is the first time that i'm
developing a complete application with it. I trie the dbengine.idle
statement and didn't work. The reason that i'm using unbound forms is
because before i started the application i started reading a book
about programming in access (specially creating multiuser
applications, which is what i need), one of the advices that the
authors give on the book is working with unbound forms, so i start
playing with them and at the beginig i like them (mainly because of
the freedom that they gave on using a single form to edit or add data
to the table without the need of specifying in which mode to open the
form, or in the case of edit mode always need to deal with the 1st
record of the table) but as i was working it started to get a litle
more complicated that i excpected (for example the sql commands to
open the recordset did'nt work properly that's why i'm dealing with
the connection object, at least that was the only solution that i
could come up with), still i would like to keep the application as it
is since the users started to use it and they like the way it's
currently working. they just ask me to add the functionality of be
able to add records to an lookup table which is where i'm stuck on.
Also one of the other recommendation on the book was to move away
from DAO and start using ADO.

Actually, I don't agree with the author's advice to use unbound forms,
though it's certainly an approach that I understand -- more so when
dealing with a client/server data store like SQL Server. But in
general, my policy is to let Access do what it was designed to do
wherever possible. There are many techniques for working with multiuser
databases, even using bound forms. And I certainly don't agree with the
author's recommendation to move from DAO to ADO, if you're working with
MDB files. Even Microsoft has backed away from that recommendation.

Please correct me if I'm wrong, and I really don't mean to give offense,
but it sounds to me as though you have programmed quite a bit of code
that you don't fully understand, and now you're being bitten by issues
stemming from the complexity of that code. It's not really possible for
me to debug the code without seeing it, and there's too much of it for
you to post it all, even if you wanted to. All I can say from the
information available is that I believe that you need to update your
lookup tables using the same connection that Access is using, if you
want your updates to be immediately visible in combo and list boxes. So
if your combo box uses a rowsource that pulls data from a linked table,
use that linked table to update the table, and use the CurrentDb.Execute
(DAO) or CurrentProject.Connection.Execute (ADO) method to do it.

 

[Guest]

Sorry, I'm a newbie and don;t know how to create a new thread but it looks
like there's some good expertise out there so here i go ...

If you look at Access 2003's help function and type "temporarily open a form
as a dialog box", you'll see at the bottom it mentions setting the form's
VISIBLE property to "No". I had a macro which did this but after installing
Access 2003, the macro no longer works - the reason I believe is that the
form no longer has a property called "visible".

I don't know anything about VBA which is why i stuck with a basic macro for
this use - is anyone able to offer advice and/or a solution?

Thanks,
SFR

 

[Dirk Goldgar]

Sorry, I'm a newbie and don;t know how to create a new thread but it
looks like there's some good expertise out there so here i go ...

It's a bad idea to piggyback on old threads, not least because your
message is likely to be viewed way down at the bottom of a list sorted
by thread and date. I don't use the web newsreader, but it really
shouldn't be hard to create a new thread.

If you look at Access 2003's help function and type "temporarily open
a form as a dialog box", you'll see at the bottom it mentions setting
the form's VISIBLE property to "No". I had a macro which did this
but after installing Access 2003, the macro no longer works - the
reason I believe is that the form no longer has a property called
"visible".

I don't know anything about VBA which is why i stuck with a basic
macro for this use - is anyone able to offer advice and/or a solution?

I don't have Access 2003 installed, but I think I would have heard if
the Form object no longer has a Visible property. Please give the
details of your macro, and explain exactly what happens when you run it.
"No longer works" isn't very informative.