Hi Jez,
Some years ago I constructed a property web site + database. I designed a number of .asp pages to enable the site administrator to upload image and pdf files of property details and store details in a database - bits of this is what I think you are looking for. The web server supported...
For anyone following this thread - the problem was with the Access2000 connection to SQL2000 running under Windows 2000 Server + SBS (but still don't know why).
A client PC with just Access2000 loaded replicated the problem (unable to open server objects in design view or run procedures).
When...
Believe your problem is due to the Recordset.Clone being updated.
Try getting the data directly from the server, thus
Dim rst As ADODB.recordset
Dim myStr As String
Dim stLinkCriteria As String
Set rst = New ADODB.recordset
myStr = Replace(Me![SDist], "'", "''")
rst.Open ("Select...
Concurrence (writeconflict) issues with Access is a BIG subject. If you have a copy of Access Developers Handbook by Litwin-Getz-Gilbert refer to chapter 6, Volume 2 (Enterprise Edition). If you don't, and want to use Access to develop SQL Server applications, I strongly recommend you purchase a...
Thanks for your reply cmmrfrds
The client PC's are connecting directly to the SQL2000 server via the Access.adp, the clients therefore should not need any of the SQL 'bits' - should they? other than mdac v 2.6 or higher ?
However, the original SQL Db was developed on SQL7 and then moved onto...
I have an SQL2000 Db with an access.adp front end which works fine on the server, but on client PC's I can't open tables in design view or run stored procedures (other than under VBA control with a currentproject.connection). On the client PC's the procedures appear in the database window with a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.