Wrox Programmer Forums
|
Classic ASP Databases Discuss using ASP 3 to work with data in databases, including ASP Database Setup issues from the old P2P forum on this specific subtopic. See also the book forum Beginning ASP.NET Databases for questions specific to that book. NOT for ASP.NET 1.0, 1.1, or 2.0.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Classic ASP Databases section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 29th, 2003, 06:06 PM
Registered User
 
Join Date: Sep 2003
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default Persistent Disconnected Updateable Client Recordse

I am writing a Microsoft web application, using Visual Studio 6, ASP, ADO, SQLServer 2000, and IIS5 on W2K Advanced Server.

The application relies heavily on client-side scripting, and uses the RDS DataControl to create disconnected client recordsets.
The user does create some new records which have to be inserted into the server base tables every now and again.
All tables have foreign keys linked to autonumbered primary keys, necessitating server round-trips to get the autonumbers.
The recordsets are used in several html pages, and need to be persisted on the client in between page requests.
The queries creating the recordsets use multi-table joins with complex DISTINCT and WHERE clauses.

I have run up against some practical problems with RDS that were not immediately obvious when I started.

1 I have found that if the RDS DataControl URL property is used to create the recordsets,
    then subsequent submitchange operations fail if the original queries included DISTINCT clauses.
    Is this normal behaviour, or am I doing something wrong?

2 I have found that if the server/handler/connect properties of the RDS DataControl are used to create recordsets via msdfmap.ini,
    then the mouse cursor flickers unacceptably on each of the 15 queries per page.Is this to be expected?

3 All attempts to persist recordsets on the client by using the fso object have resulted in the following error:

    "The safety settings on this computer prohibit accessing a data source on another domain".

    This happens even if the data is on a non-domain local computer, and "Access data sources across domains" is enabled in IE5 or IE6.
    Again I need to know if this is expected behaviour or if I am doing something wrong?

I have invested much time and effort in RDS and don't want to "move on" unless I am sure on the above points.

If these RDS problems are insurmountable, I need to know the quickest,least expensive and best way to generate persistant client recordsets.
I have seen some articles creating disconnected recordsets using XML, but nothing on getting autonumbers or updating base tables.

I am on a low budget and assume that I cannot afford to invest in Visual Studio.Net.
Because of my RDS experience I am wary of new technologies, and being self-taught need good documentation to help me.

What would you do in my position?



Donald Cruttenden





Similar Threads
Thread Thread Starter Forum Replies Last Post
Persistent URL (P.U.R.L) sloesch VB.NET 1 January 23rd, 2006 11:57 AM
Persistent Classes?? MAtkins General .NET 8 December 15th, 2004 04:00 PM
Updating disconnected datasets AgentSmith ADO.NET 7 July 26th, 2004 10:37 AM
Persistent Disconnected Updateable Client Recordse doncrut XML 0 September 29th, 2003 06:10 PM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.