Problem is,

College is running Office 97, and at home im running Office XP.

ive already asked gary about this, he said there not a chance it'll work.

Anyone shed any light on my problem

Si

 

Yeah your versions are different..

see office xp aint the same as 97..

You follow that??

or..

version is difrent.

cant work dont think..



Make sense?

David

 

David's right. Access 97 and Access 2002 (aka XP) aren't compatible, as far as I'm aware. You may, however, be able to save your databases as '97-compatible from OXP. I don't know, though, as I don't use Access (it's a POS).

Surely though, referring to your other thread about W2K vs XP, if the college is running Access '97 you should be running it at home too? Or do you have an inconsistent policy?

 

word 97 and 2002 works! :P

I think they changed from DAO to ADO in these two version.

College it slowly upgrading to win 2k and office 2k.


Si

 

By that logic, I could come back and say that stuff that runs on W2K will also run on XP.

 

i might put XP back on, just had few issue's with games.

 

its got nothing to do with ado and dao, its because micro****e are *****..

same prob with access 2.0 and 97 etc.

Word documents arent quite as complicated as databases..

David

 

LOL. Most games run better on XP than W2K. If you were comparing XP with 98, I might agree that the latter is a better gaming OS. But not XP.
Sorry to disappoint, David, but the format of an MS Word document is far more complex than an MDB file. I know - I've written an import filter for word files.

 

just i bought to 2k so id might aswell use it.

I know Xp does use the ADO, 97 doesnt support that.

Whats worse is the college is on NT and its fooking ****.

Just sorted my database out at last.

Im am suprised word is more complex, but i suppose it has more options and use's.

Si

 

Tools, Database Utilities, Convert Database, To Access 97 File Format ...

Of course, if you've used any new features that aren't supported in Access
97, the app isn't going to work without modification.

There is an interesting feature that may help you, if you look between the Escape key and the F2 key and press the button. Alternitavely STFI

 

Si,

It aint an ADO/DAO problem, I use ADO to connect front ends to Access97/2000/SQL Server, ADO just supercedes DAO, its basically the MDB file format changing, your best bet is to design it in '97 and then you can open in 2002 you just wont be able to change the structure, how did you get on with the DB anyway, you understand the relationships now yes?

Gary

[Edited by GaryK - 9/17/2002 3:09:16 PM]

 

No, the reason it's more complicated is because of the way it stores the data. Firstly, it uses a technology called 'fast saves', where it stores deltas (changes) to the document at the end of the file, and only ever rewrites the entire file every now and again. This means that, for example, if you have a 500-page 10Mb document, and you make a 2-line change on page 30, all Word does is open the file and write that change to the end, and close it again. It makes it much faster, but means that to correctly read the file you need to stitch together all the deltas correctly, which is no mean feat, and requires a complex state machine for the document parser.

To complicate things further, the file format is designed in such a way that, for example, if you wanted to print page 450 of your 500-page document, the entire document doesn't have to be read from disk. This means that each of the streams of text/formatting, and the deltas, have dependencies and relationships which have to be fathomed out before you can get at the text itself.

It's a very clever format, but probably overcomplicated (particularly when machines and HDDs are so fast these days that saving the whole of a 100Mb document wouldn't take long anyway).

[Edited by MarkO - 9/17/2002 3:11:10 PM]

 

yeah Gary is cracking now Works propper good.

just got the time consuming vb forms to write!



Sorry rushed the gif in paint
Si