Odd Problem -- Data Provider Bug?

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   VBA Environment; AXP

2 Back End Databases; Main and Calendar.

I have a multi-resource schedule, using DAO to manipulate 1 extra field (RN) placed in the event table of the calendar database.

 The problem:
 If I persist a connection to the Event table in the calendar database, the calendar control takes forever to right to the table. Sometimes up to 30-40 seconds.

Example:
Set rstSXPLink = db.OpenRecordset("Event", dbOpenDynaset)

As soon as I close the recordset, which I don't want to do, the control writes to the table instantly.

I need to persist a DAO connection to the calendar db, as this significantly improves performance, and I need the control to write to the table as soon as .DataProvider.Save excutes, in order for my code to find the EventID and Place the linking number in RN. If the control has not written to it's table by the time my code looks, it fails to link.

Any idea??

Robert

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
rgracie Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 12 November 2006 Status: Offline Points: 75	Post Options Post Reply Quote rgracie Report Post Thanks(0) Quote Reply Topic: Odd Problem -- Data Provider Bug? Posted: 28 March 2007 at 7:37pm
	VBA Environment; AXP 2 Back End Databases; Main and Calendar. I have a multi-resource schedule, using DAO to manipulate 1 extra field (RN) placed in the event table of the calendar database. The problem: If I persist a connection to the Event table in the calendar database, the calendar control takes forever to right to the table. Sometimes up to 30-40 seconds. Example: Set rstSXPLink = db.OpenRecordset("Event", dbOpenDynaset) As soon as I close the recordset, which I don't want to do, the control writes to the table instantly. I need to persist a DAO connection to the calendar db, as this significantly improves performance, and I need the control to write to the table as soon as .DataProvider.Save excutes, in order for my code to find the EventID and Place the linking number in RN. If the control has not written to it's table by the time my code looks, it fails to link. Any idea?? Robert