Code wont work in ADP

[Guest]

Greetings all. If something is possible in MDB is it also possible in ADP.
Since upsizing I have found that some things no longer work, like my
cascading combo boxes. When I look at the code it does not even look the
same. Are there limitations with ADP that can not be overcome? We have had
so many problems with Jet that I am glad it is gone, and I do not want to go
back, but we miss our old forms. Thank you in advance.

 

[Arvin Meyer [MVP]]

Jet is not gone and you can use both (although not in an ADP). It isn't so
much the ADP that's limited as that there are some things which can only be
done in DAO (and not in the ADO required for ADPs) Most things do work or
can have workarounds. Cascading combos require multiple trips to the server,
the same way they did with Jet. Use the combo's AfterUpdate event to refill
the next combobox.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Guest]

Thanks for the input. I was under the impression that with SQL 2K as the
back end and using ADP I would not be using the Jet engine. Is this not the
case? The reason I started using ADP instead of MDB is that even after
upsizing to SQL Server I, and all of our users kept getting the message that
says something like 'you can not do whatever you were trying to do because
multiple users were trying to update the same record', even when I know I was
the only one on that record. Once I switched to the ADP I have not gotten
one such error. From everything I have read here since I started using
Access I thought those errors were a limitation of Jet. Have I been wrong?

 

[Sylvain Lafontaine]

The message "you can not do whatever you were trying to do because multiple
users were trying to update the same record" is usually the fact of a
missing primary key. Make sure that the upsized table has its primary key.

For Views, take a look at the following article:
http://support.microsoft.com/kb/q209123/

For ADP, there is a newsgroup about ADP: m.p.a.adp.sqlserver. On Google:
http://groups.google.ca/group/microsoft.public.access.adp.sqlserver

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

 

[Arvin Meyer [MVP]]

That message occurs because you've either opened the same page of data for
editing twice (2 bound forms editing the same data) or because you don't
have an identifiable index (primary key) in a query that you are trying to
edit. If you use unbound forms with a defined key to edit, you probably
won't ever see that message.

ADPs use only ADO. Jet is used as an overlay to SQL-Server when you use an
MDB as a front-end. You may want to do that for reporting or for certain
update queries because you can use custom VBA functions with Jet and you
cannot with SQL-Server.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access