Showing posts with label back-end. Show all posts
Showing posts with label back-end. Show all posts

Tuesday, March 20, 2012

Access/SQL "Write Conflict"

Hello,
I'm using a Access 97 Front-end and a SQL Server 2000 back-end.
When entering a subform on a form, information has to be saved to the
database.
But when entering the subform I get a "Write conflict" error in Access.
In SQL I'm using 3 tables with 1 view defined on those 3 tables. I use
INSTEAD OF INSERT/UPDATE/DELETE triggers to handle
INSERTS/UPDATES/DELETES.
In Access I use that View as a Source for the form.
Does anyone know why I get this error?
Roy
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
When I followed the execution of the code, I saw that the "Write
Conflict" error appeared after the following sub executed:
Private Sub Form_BeforeUpdate(Cancel As Integer)
If Me.Dirty Then If ap_ConfirmAction(Me, apUpdate) = vbNo Then
DoCmd.RunCommand acCmdUndo
'###ROY TOEGEVOEGD VOOR GENEREREN GUID
If IsNull(Me.dummyveld) Then
Set ObjGUID = CreateObject("event.util")
GUID = ObjGUID.GetNewGUID()
Me.dummyveld = Mid(GUID, 2, 36)
Set ObjGUID = Nothing
End If
End Sub
After the "End Sub" the "Write Conflict" error pops up.
I hope someone can help me.
Roy
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Access/SQL "Write Conflict"

Hello,
I'm using a Access 97 Front-end and a SQL Server 2000 back-end.
When entering a subform on a form, information has to be saved to the
database.
But when entering the subform I get a "Write conflict" error in Access.
In SQL I'm using 3 tables with 1 view defined on those 3 tables. I use
INSTEAD OF INSERT/UPDATE/DELETE triggers to handle
INSERTS/UPDATES/DELETES.
In Access I use that View as a Source for the form.
Does anyone know why I get this error?
Roy
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!When I followed the execution of the code, I saw that the "Write
Conflict" error appeared after the following sub executed:
Private Sub Form_BeforeUpdate(Cancel As Integer)
If Me.Dirty Then If ap_ConfirmAction(Me, apUpdate) = vbNo Then
DoCmd.RunCommand acCmdUndo
'###ROY TOEGEVOEGD VOOR GENEREREN GUID
If IsNull(Me.dummyveld) Then
Set ObjGUID = CreateObject("event.util")
GUID = ObjGUID.GetNewGUID()
Me.dummyveld = Mid(GUID, 2, 36)
Set ObjGUID = Nothing
End If
End Sub
After the "End Sub" the "Write Conflict" error pops up.
I hope someone can help me.
Roy
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Monday, February 13, 2012

Access front-end to SQL back-end

I'm new to SQL Server 2000. I decided to purchase this server because
my old company (UPS) used the server to help expedite queries and
manage on-line reporting. So, now it's up to me to utilize and
understand the new server. I have been using MS Access as my front-
end for several ad-hoc databases, so I'd like to keep utilizing this
method. I want to test my first database using the SQL Server.
I've got everything set up. The IT department has installed the
server software on my computer. Within my Access database, I link in
tables from a database called "Progress" using a Merant driver.
Queries, forms, macros and modules are all pulling from these "linked"
tables. Do I need to link these tables into the SQL Server? How do I
transistion this database over to SQL? I guess I'm confused about the
relationship of how all of this should work.
Right now it looks like this:
PROGRESS .... linked...... MS Access ...... reporting/results
Where does SQL fit in?Hi,
What you need to do is migrate your database from whatever RDBMS you are
using to SQL Server. That means transferring the structure of your
database as well as the data. I don't know what RDBMS you are using so
I can't give you detailed instruction on how to do it. Essentially you
need to put your existing RDBMS out of service in favor of SQL Server.
So you can't link the exsiting "tables into SQL Server". You have to
transfer them completely.
A number tools exist for transferring data to SQL Server including bcp,
and DTS/SSIS.
Jonathan
mssbass wrote:
> I'm new to SQL Server 2000. I decided to purchase this server because
> my old company (UPS) used the server to help expedite queries and
> manage on-line reporting. So, now it's up to me to utilize and
> understand the new server. I have been using MS Access as my front-
> end for several ad-hoc databases, so I'd like to keep utilizing this
> method. I want to test my first database using the SQL Server.
>
> I've got everything set up. The IT department has installed the
> server software on my computer. Within my Access database, I link in
> tables from a database called "Progress" using a Merant driver.
> Queries, forms, macros and modules are all pulling from these "linked"
> tables. Do I need to link these tables into the SQL Server? How do I
> transistion this database over to SQL? I guess I'm confused about the
> relationship of how all of this should work.
>
> Right now it looks like this:
>
> PROGRESS .... linked...... MS Access ...... reporting/results
>
> Where does SQL fit in?
>