Access 2000

[Lorna]

I have developed an application in Access and made the original copy on my PC, the Design Master. I've also replicated the database so that these versions can be installed on user's PC.
Now - on my PC the Design Master (with DAO 3.51) AND the replica works fine. BUT on user's PC does not work correctly. If I acces the Design Master via the network from a user's PC, it automatically references DAO 3.6 ?? Is this ok?

I find that if I remove this reference, the system works fine EXCEPT for where I create recordsets (obviously).

I have no idea what the problem is - everything works on my PC, but not on user's. (My problem - I've got a listbox on which I test for NOTINLIST event - in replica's this doesn't work.

ANy advice pse? I'm desperate.

Thanks

[robby bassic]

I'm at the last leg of a huge contract, and my client convinced me to make a Replica and Design Master. What a mistake!!! I'm learning to live with it.

Are the users not networking off of a common database?

Either way, whenever you reference a new library you must do so on each station, unless you package it with a developers edition.

If for some reason a user is missing an OCX or DLL you should install it for them(try always for same version).

If your client is using one common database and its not too late I would revert back to a regular setup (get rid of the Replica). You can just keep track of all the changes that you make then update the clients' copy.

P.S. When you eventualy install the Design Master at the clients', you will not be able to modify it from your office.(unless on-line)

[Lorna]

I thought replication was Developer's Heaven, but obviously it's not!!

As I'm a beginner I'm a bit stupid with this Access thing. Yes the user's are all using a common networking drive for the database. I'm not sure what your relevance of this question is?

How do I reference a new library off a user's terminal if they've only got a replica (cannot get into VBA code to get to the reference menu)
Also - how do I know which OCX or DLL is missing and how do I copy it to them (remember this is all written in Access and VBA?)

If I do what youre suggesting - then I copy the disgn Master to all users and if I make changes, I do it on my terminal and then overcopy it to their's?

Sorry for all the dumb questions

Lorna

[Lorna]

Sorry Robbie, just to make it all a bit clearer...

the design Master is on my local PC. The Backend (tables etc) lies on a common server. So the idea was to install only a replica of the front end on every users pc.

Or is it a better Idea the chuck to whole lot (designmaster-front end and back end) on the server and on each users' desktop just to link to that? Is that not going to be very slow?

How would you set this up?

[robby bassic]

You can reference on a replica. Hold Shift key down as you hit the short-cut to get in, then goto Forms or Reports section, then the icon for VB will be enabled, (it will warn you that you can't make changes) you can now access the references.

The reason I asked about networking, (I wasn't being condescending) I just wanted to make sure that all the users were all using the same DB.

Didn't you notice, when you made the replica the file size almost doubled. Mine is at 400 megs compressed.

[robby bassic]

If you are willing to scrap the replica then do this:

Put your entire project back-end and front-end into one database. Copy it onto the clients' server and give each user a short-cut to it on their desktop. Of course you will have an identical copy of it in your PC. Each time you make a change (keep track of all of it) just install the new objects into their system (the VB code will follow the obects whereever they go.)
And don't use linked tables unless you are knowledgeable on the subject.

[robby bassic]

Me again.

It won't be slow at all, if anything it should be faster.

I forgot to mention, Has there been a lot of data entered since the DB was replicated?

If the tables were not setup correctly for the replica, the autoID numbers are probably now random instead of incremeting.

[Lorna]

hi

1) No there has not been a lot of data enterend. Fortunately, we're still in testing phase - nothing is live yet.

2) By chance, the autoID numbers are still correct - not ramdom. Good luck I suppose!

3) You say combine front and back end into one database - does that not make the security a problem (anyone can then access the tables/design etc?)

Thanks again

[Judgey]

Hi Lorna,

I have had a similar problen to youself with VB front ends using Access 97 & 2000 on other colleagues machines, the common denominator was always they had come back from IT with windows re-installed. This ment that previous versions of MDAC which I my VB program had installed had not been put back on, DAO 3.51 I think useds MDAC 2.0 / 2.1 wheres as Access 2000 uses MDAC 2.5 /2.6 components, if you install MDAC 2.0 or 2.1 this should resolve the problem.

[robby bassic]

What Judgey replied is exactly true.

As far as sercurity, you will have to invoke it. Lucky that you are using Access2000.
The wizard is excellent for this. Make sure that you are the 'owner'.

I suppose that on load of your app. a Main form does display to user, if so, I would in Tools\Startup uncheck 'Display Database Window',
and anything else that you want to hide(you can virtually strip it down).To go in yourself and see the database window, hold the shift key while entering from short-cut. And on your Main form/Properties/Allow Design Changes select 'Design View Only' , so the user can not right-click and see properties.