import problems

[Bibi]

Oh boy...this is so stange - I created a series of new tables, queries forms
and reports for an existing database. I was able to successfully transfer
all the new items EXCEPT the major dataentry/dataupdate form. It does
transfer successfully from one computer to another at other sites but not at
the end users! They are on a sophisticated server system....so I thought it
could be related to some security feature - however I tried to create a
simple form based on the new table directly into their database on the server
and again it caused the Error/crash scenario. The only thing different about
this table from any other table I have ever created is that it has three
primary keys. Could that be an issue?
Please help!
TIA
Bibi

 

[Larry Daugherty]

You can have exactly one Primary Key in a table. That Primary Key can
be made up of several fields.

It may be a security issue but you haven't fully characterized the
symptoms. What all *does* work and what all *doesn't* work. Possible
that you're dealing with a virtualized folder?

HTH

 

[Bibi]

Larry
Thank you for the prompt input - I see the distinction you've made - I have
one primary key consisting of three fields.
Because all the forms and queries run on my, and other outside, computers
and I have only limited time on the users' system- a quick and simple answer
is difficult - on the users' server we can input data into the table and I
can generate reports based on the table - BUT working on the users' server I
am not able to create a form based on the table - I need a data input form
for the end users and am at an impasse. .......what is a virtualized folder?
I am self taught and have many gaps in my understanding of Access.
TIA
Bibi

 

[Larry Daugherty]

It sounds like there is an awful lot in the configuration of the users
hardware and operating system that you assume we know. Until you
explain it all to us, we don't know and, therefore, we can't help
much.

I'm assuming that you have split your application into a BackEnd which
resides on a shred folder on the server and that every user has their
own copy of the FrontEnd. By the way, those FrontEnds should be
compiled and make into MDE/ACCDE before distribution to the users so
that no one can make design changes to them. As the developer you
should be the only one with an MDB or ACCDB so that *you alone* can
make design changes.

When the current issues are resolved you might go to Tony Toews' site
and look for his Front End Updater. It handles a lot of multi-user
application issues and is freely downloadable and modifiable to suit
your client configuration.

Tell us everything about the client configuration. Both hardware and
software. What OSes are running on the PCs and on the Server? Why
are you trying to do design on the server? Is the fully enabled
MSACCESS.EXE actually running on the server? Why is your access to
the server so limited. If nothing else can't you set up or have their
system administrator set up a Remote Desktop for you?

A virtual folder isn't actually where you think it is. Windows Vista
puts things where it has decided they should be and it imposes
security and miss-direction. I haven't played with Windows Server
2008 but I'd have to believe it's very like Vista.

When next you write, please include the exact wording of the error
message. "Error/crash" doesn't convey much meaning.

What are the "other sites" as compared to the "end users"? What do
you mean "transfers well"? What do the "other" sites do that the "end
users" doesn't do?

HTH