Re: Strange fault
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Fri, 10 Feb 2006 12:10:35 -0500
Very strange that you couldn't set the UniqueTable property in code, first
time that I see this. In what event did you try to do this?
For your ResyncCommand, you can try something like this:
"SELECT * FROM [C - Giornale] WHERE [ID giornale] = ? "
Access should replace the ? with the value of the primary key for the
current record. However, as you have some trouble with the UniqueTable
property, I'm not sure if this will work. Also, personally, I prefer to use
a stored procedure and set this value for the form with something like:
MyResyncSP ?
For the question about the support from MS; it's look like that MS has
dropped the ball in favor of .NET or for those who insists to use Access, in
favor of ODBC linked tables in a MDF file; so don't expect to see any ADP's
problem solved (and quite probably, this will also be true for the next
version of Office).
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
"Atlas" <atlaspeak@xxxxxxxxxxx> wrote in message
news:11uop66mhllnvda@xxxxxxxxxxxxxxxxxxxxx
Creating a ResyncCommand and setting the UniqueTable property correctly
Ok I couldn't set programmatically the uniquetable property (errors),
nevertheless placing the following command in the form's beforeupdate
event solved the problem.
Me.ResyncCommand = " SELECT * FROM [C - Giornale] WHERE [ID giornale] =
" & Me.ID_Giornale
There's a slight "flash" when the command is executed......but it works!
And it looks like only that record is requeried, not the whole recordset.
One funny beheaviour: I've began setting the me.ResyncCommand in the
form's Load event; obviously it wouldn't work because the field
Me.ID_Giornale was set at load and never changed, hence the resynched
query would load always the first record int the recordset and MAGIC:
multiple instance of the first record would appear!!!!
Strange no?
Another strange thing is that the form did'nt have any multitable or
innerjoined table. The problem arised only when a WHERE clause was
specified.
What is unbeleivable is that since jan 2005 they didn't fix the problem
that occurs only in access 2003.
Did they decide to abandon the pot?
.
- Follow-Ups:
- Re: Strange fault
- From: Atlas
- Re: Strange fault
- References:
- Strange fault
- From: Atlas
- Re: Strange fault
- From: Sylvain Lafontaine
- Re: Strange fault
- From: Atlas
- Re: Strange fault
- From: Sylvain Lafontaine
- Re: Strange fault
- From: Atlas
- Strange fault
- Prev by Date: Re: access as frontend to backend sql 2000
- Next by Date: Re: Data Access Page won't reconnect
- Previous by thread: Re: Strange fault
- Next by thread: Re: Strange fault
- Index(es):
Relevant Pages
|