populating forms

[smk23]

I have an MS Access 2002 frontend app that schedules and
tracks events in an office with a SQL Server 2000 DB on
the backend. Currently, I have exceeded Access' max file-
handling capacity, resulting in inability to edit records,
add new records, or delete records from the Access forms.
This happened suddenly after running these forms for
several years and followed restructuring of the backend DB
which increased total number of fields in the DB.

My solution would be to handle all sorts and filters on
the SQL backend and decrease network traffic and hopefully
improve performance on the frontend.

Access Project looks worthless to me because it is single-
user (this blows me away!!) for record editing
capabilities. That leaves me with using ADO objects in
the .mdb app to populate forms, right?

Anybody out there want to comment on this?
Thanks,
smk23

 

[Albert D. Kallal]

Access Project looks worthless to me because it is single-
user (this blows me away!!) for record editing
capabilities.

HUH?

Time to get some training, books, or learn how to use a database! ADP are
designed to work native with sql server, and it the results are most
certainly multi-user. In fact, we have seen credible reports of have 1000+
users at the same time when using ADP projects. They are scalable, secure
and robust.

 

[Guest]

"the books" is where I discovered this info.
smk23

 

[Albert D. Kallal]

Well, whatever your source of info, they are dead wrong.

ADP projects in ms-access are most certainly multi-user.

In fact, I once could argue they are MORE capable at multi-user database
applicatons then is a JET file share. ADP projects are designed to work very
tightly with sql server, and that is Microsoft's premier multi-user database
system.

There is not much more that needs to be said here. I mean, the old saying
about you can lead a horse to water......

Anway, ADP projects are multi-user.