[AccessD] access97 application on win2000

It was only happening on W2k machines, but there was another quirk.  It was
occurring on a database that people were opening a link to from an intranet
page.  They were getting the Open From location or Save options.  The Open
option was opening to instances of the database, the first 'locked', the
second got the error.  When I switched the code, the first still locked, but
the second opened.  When the second instance was closed by the user, the
first instance closed too.  It was wierd.
 
I do know that Jet 3.51 has a quirk in MDAC 2.5 (and I think up to 2.7), I
always use Jet 4.0, but that's with ADO, not DAO.
 
Drew

-----Original Message-----
From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com]
Sent: Tuesday, June 17, 2003 6:58 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] access97 application on win2000


Rats.  I would hate to do that because I've moved the app to A2K and they're
still on A97.  Was the problem associated with W2K?
 
Rocky
 

----- Original Message ----- 
From: Drew Wutka <mailto:DWUTKA at marlow.com>  
To: 'accessd at databaseadvisors.com' <mailto:'accessd at databaseadvisors.com'>  
Sent: Tuesday, June 17, 2003 1:22 PM
Subject: RE: [AccessD] access97 application on win2000

Yes, don't create a variable to reference CurrentDB.  Just use the CurrentDB
object.  I had this happen to one of the databases (before my starting here)
that had an Access created switchboard.  The switchboard code failed on the
set db=currentdb line, so I just removed db in all places and replaced it
with just CurrentDB.  Worked great.
 
Drew

-----Original Message-----
From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com]
Sent: Tuesday, June 17, 2003 2:12 PM
To: AccessD at databaseadvisors.com
Subject: [AccessD] access97 application on win2000


Dear List:
 
Does anyone know the answer to this one?  
 
 
MTIA,
 
Rocky Smolin
Beach Access Software
 
----- Original Message ----- 
From: Dave  <mailto:dmcdonald at trci.net> McDonald 
To: Rocky Smolin <mailto:bchacc at san.rr.com>  
Sent: Tuesday, June 17, 2003 11:56 AM
Subject: Fw: access97 application on win2000

Rocky,
 
I found some else with a similar problem.
 
Dave
----- Original Message ----- 
From: Dave  <mailto:dmcdonald at trci.net> McDonald 
To: "Victor" <mailto:vescalera at apelcan.com>  
Sent: Tuesday, June 17, 2003 2:00 PM
Subject: RE: access97 application on win2000

Hello Victor,
 
If you ever get an answer, please pass it on to me.  I have the same
problem, running Access97 in Windows2000.  Tried removing and re-installing
Access and W2000.  No help.  I used to get the "ActiveX component can't
create object" (Error 429).  Debug would take me to the same location as you
in the mdb , Set db As database()
Set and rerun would not help.
 
Now Access won't even open the mdb.  I get a message 
"<process has already exited> has generated errors and will be closed by
Windows" which it does. 
 
Please pass any advice along to me.
 
Thanks,
 
Dave dmcdonald at trci.net <mailto:dmcdonald at trci.net>  

-----Original Message-----
From: "Victor" < vescalera at apelcan.com <mailto:vescalera at apelcan.com> >
Sent: 6/16/2003 1:00:44 PM
Subject: access97 application on win2000

I have an access97 application perfectly running on win95, win98 and winxp,
but no on win2000 (at least in the server edition).
If I execute the application on win2000,  it spends several seconds (with an
intensive use of the hard disk) in the instruction:

set db= currentdb()  'db as an object of the database.

.... and finally  the application is closed without messages.

In the original application I used DAO 3.51. In win2000 DAO 3.6 is marked in
references.
I have installed the MDAC 2.7 but the problem is not removed.

How can I solve the problem?

Thanks
Victor


.




  _____  




_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030617/8e9141c2/attachment-0001.html>