access 97 to a2k vb not working

[craw]

i have created a database using A'97. it's a split database with the be on a SQL server - used in a multi user environment. i'm set as the database owner on the server. however i have created a user group on the server that allows editing (create/delete/change records). i did two tests today. one with on a computer using A2k and the other using 97, same permissions, etc. i've noticed certain features not working:

for example. i have a subform on delete event that opens another form to a specific record... in 97 it works - in A2k it doesn't.
another example, i have two forms used to input new data. the first form's data is saved in one table called tbl_generalinfo the next form saves data in tbl_toolbookinfo. the first form stays open but hidden when the user clicks the "next" button - the user can make changes in the second form and then hit "done". at which point both forms are closed and data is saved, right?!! Wrong - the info input into the first form does not show up but the second form does. and as before, it only does this in the A2k version. i have tried on open, converting the database for the A2k user and i have tried leaving it as is... the same problems arise.

i only have a one or two users who need to have editing rights... so i'm probably going to have A2k removed from their machines and replaced by A97. i just hate to let Bill and his gang stump me on this one.

any suggestions/help would be greatly appreciated.

 

[craw]

could it be which DAO library i'm using

i'm using DAO 3.51 Library in A'97... would that make a difference to my editing A2k users?

 

[Stephen C Smith]

Access 2000 was a big upgrade from '97 in that it changed from DAO data objects to ADO data objects. If you upgrade a database from '97 to 2000, you might want to check the references and make sure that you have DAO rather than ADO data objects checked (unless you want to re-write your code).

Not sure if the above is specifically related to your problem, but I used to have all kinds of odd problems solved by fixing references when I upgraded an app from '97 to 2000.

Concerning the problem of the data on the first form not being saved, try putting a Me.Requery in your code behind the "next" button BEFORE opening the other form. I used to have stuff not save on a form - that seems to fix it. Make sure it is before opening the form!

Hope that helps,

Steve S.

 

[craw]

you might want to check the references and make sure that you have DAO rather than ADO data objects checked

do you mean while on the computer that has A2k?, check the Tools<References<References Available<(choose Microsoft DAO 3.51 Object Library)

Concerning the problem of the data on the first form not being saved, try putting a Me.Requery in your code

wouldn't i get the same error/problem when using my A97 fe? i don't have the me.requery in my A97 fe and it works like a charm. i'm going to get on the other machine and check out the DAO library... although i'm not sure if i understand yr suggestion on that one.

i'll give it a try and let you know.

thanks, SCS

 

[craw]

correction- it's A2002 not A2k

sorry sorry, i made a mistake, it's not A2k, it's A2002. (i am using A97... there's no mistake in that one ) Also, i just checked to see which reference library the A2002 user has, it's DAO 3.6. Which should be able to read/interpet my DAO 3.51??

 

[ChrisO]

G’day craw

Not only will you need to have DAO referenced but it will also need to be a higher priority than ADO if ADO is referenced. Seldom did people disambiguate DAO in A97 because there was no need.

It was written as: -

Dim dbsMyDatabase As Database
Dim rstMyRecordset As Recordset

But in higher versions that have ADO as well as DAO referenced, DAO would need to be the higher priority IOR you will need to disambiguate as in: -

Dim dbsMyDatabase As DAO.Database
Dim rstMyRecordset As DAO.Recordset

Hope that helps.

Regards,
Chris.

 

[craw]

ChrisO~~~
it's not brushfire season is it? i have a couple of friends who live on yr side of the world!

thanks for the advice... my editing user does have the DAO 3.6 library checked on his computer but it's about third in the list. i will try moving it up to the top.

isn't it strange that i wouldn't get an error msg? it just doesn't save the record on the first input form but does save the data on the subsequent ones.

 

[craw]

i was unable to get DAO to move on the priority list for my A2002 user

 

[ChrisO]

G’day craw

We have had a very mild summer so far so not too many bushfires thank heaven.

DAO as third on the list should be about as high as it will go, it should only need to be higher than ADO if present.

I’m only running A2K at the moment so I may not be able to help with this but if you could cut down an A97 sample and post it then others may be able to have a look at it.

Regards,
Chris.