Access or SQL server issue?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I constructed another database and then migrated it to
SQL server. Once on the server, I cannot edit tables, views, and reports,
although I can make and save forms that are viewable only to me. Is this an
Access issue, or is it an issule of permissions at the SQL server or file
server level?
 
SQL Server is pretty demanding about that primary key thing, so I was very
careful to make sure that each table did have them defined. As I recall, once
we got the database up and working on the server, I was able to edit at the
beginning. I tend to think that the current problem is arising from
permission settings on the server side, but there is a question and everyone
seems to be scurrying to blame Access and find an "Access Guru" to fix the
problem. From what I know of Access (more than of SQL Server or Server
Administration) I think they're chasing up the wrong tree. Anyway, I thought
I'd ask you guys.
 
Try adding a TimeStamp Field on each SQL Server (User's) Tables. I have had
similar problems with ODBC-linked (from SQL2K) Tables until I added a
TimeStamp Field in each Table.
 
screw MDB with a 10-foot pole

use Access Data Projects
Click to expand...

Yeah, right. As long as you don't need to hook up to anything other than
ONE SQL Server database, don't need local tables, don't moind having
virtually no security on your tables, and don't mind dealing with lots of
bugs.
 
hey screw you MVP

stop letting Microsoft bully us around and start singing the praises of
ADP.
 
i mean seriously-- WHO says that; WHERE is it said and WHY

i mean-- when Microsoft starts COMMUNICATING with the Access
development community-- then MAYBE

but as it is MDB is a total joke

start usign the right tool for the job-- the right tool is ADP
 
Van

I am really curious-- where is this reccomendation PUBLIC?

I mean-- Microsoft isn't going to cancel ADP without refunding me
money. That's all I'm saying.

ADP friggin rocks and you drunk MVPs are the reason that Microsoft
hasn't taken ADP seriously.

Start sticking up for the best reporting solution in the world--
MICROSOFT ACCESS DATA PROJECTS
 
Well, if ADP is that good, you wouldn't want to start a class action again
Microsoft for bugs in ADPs, would you?

That's all I am going to say since you have made your choice ...
 
ADP _IS_ good-- but Microsoft is being too lazy.

they sit around when a new Access bug comes around.. and they say 'oh,
it's a known issue'

i just wish that you Microsofties would have to work in the real world
for a few weeks.. I have never met a single MSFT employee that is 10%
qualified to work there.

And I have never heard a MVP talking about ADPs-- i'm just curious--
why were the MVPs told not to use ADP but us mere mortals are stuck
going down a road where Microsoft refuses to fix bugs

ADP is the most important product that MS has ever come up with.

And a bunch of drunk monkeys at MIcrosoft aren't taking it seriously.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Form datasource from sql server backend 1
SQL Server Backend is Read Only 7
Best way to deploy Access read-only database that is linked to SQL tables 6
Access and SQLServer Express 2005 3
Alternative program calls 5
SQL Server connection 17
Linked SQL Tables don't report Cascading Updates and Deletes 2
Access and SQL Server 7

Back
Top