Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Multiuser / Networking / November 2003

Tip: Looking for answers? Try searching our database.

Splitting Headache---code problems after splitting

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Darby - 23 Oct 2003 19:29 GMT
So I went and split my DB like almost everybody I spoke to recommended.
But now I am having PROBLEMS with my code.
The first thing that I notice doesn't work is when my
code tries to set an index for a recordset.
I get the following error.
"Operation is not supported for this type of  object."
-----Following is the code...------
Dim dbs As Database
Dim rst As Recordset
Set dbs = CurrentDb
   Set rst = dbs.OpenRecordset("Orders")
   rst.Index = "Client Id"   THIS IS WHERE I GET THE ABOVE MENTIONED ERROR
   strSeek = Me.Client_ID
etc...
-------------------------------------
Can someone offer any ideas as to what might be the problem/solution.
And what other issues I might run into after having split my Access2K DB.

Thanks
Darby
Marshall Smith - 23 Oct 2003 19:34 GMT
Have you checked your references?  In VBA, open Tools > References.  Make
sure you have Microsoft DAO 3.6 Object Library (or the highest version of
DAO you can find) selected.  In your Dim statement, declare rst explicitly
as a DAO.Recordset or ADO.Recordset, whichever you prefer.

HTH,

Marshall Smith
Project Developers, Inc.

> So I went and split my DB like almost everybody I spoke to recommended.
> But now I am having PROBLEMS with my code.
[quoted text clipped - 16 lines]
> Thanks
> Darby
Darby - 23 Oct 2003 19:50 GMT
Thanks for such a quick response....however
I have the reference to DAO3.6
and although I didn't declare my rst explicitly as DAO
I have now tried it and I still get the same error. Even when I declare it
as ADO.
Any other ideas?

> Have you checked your references?  In VBA, open Tools > References.  Make
> sure you have Microsoft DAO 3.6 Object Library (or the highest version of
[quoted text clipped - 27 lines]
> > Thanks
> > Darby
Peter Russell - 23 Oct 2003 20:30 GMT
The one thing which is explicitly not available for a linked table is
Seek.
If you want use it you will have to open the backend database directly in
code.
Otherwise, use FindFirst.

regards

Peter Russell

> So I went and split my DB like almost everybody I spoke to recommended.
> But now I am having PROBLEMS with my code.
[quoted text clipped - 18 lines]
> Thanks
> Darby
Douglas J. Steele - 23 Oct 2003 21:17 GMT
Just to tag along on Peter's post, check
http://www.mvps.org/access/tables/tbl0006.htm at "The Access Web" for how to
do this.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)

> The one thing which is explicitly not available for a linked table is
> Seek.
[quoted text clipped - 28 lines]
> > Thanks
> > Darby
Frank Konzal - 05 Nov 2003 19:55 GMT
Have you tried deleting the links and re-linking?

> So I went and split my DB like almost everybody I spoke to recommended.
> But now I am having PROBLEMS with my code.
[quoted text clipped - 16 lines]
> Thanks
> Darby
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.