Re: Data corruption with SQL server installed
- From: Stephen Raftery <StephenRaftery@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 1 Oct 2006 02:03:01 -0700
I have tried a recompile, but the problem is still there.
By way of explanation, one of teh procedures involves adding a new record to
a table of transaction, for which I use a recordset .AddNew method. When the
..Addnew executes, it fills every field in the table with the value of the
Primary key field (which is an autonumber field), and ignores the
instructions to give the values I specify. Since some of the fields are
strings, and some are boolean, the .Update method fails.
This is quite exasperating.
Stephen
"Sylvain Lafontaine" wrote:
Maybe a mixe-up in the references: check the References in the VBA window.
and make sure that the Microsoft DAO 3.6 Object Library is selected and that
is displayed *before* the Microsoft ActiveX Data Objects 2.5 library and not
after it.
While in the VBA window, it might also be a good idea to make a full
recompilation: add a dummy reference in the references window and then make
a full recompilation from the Debug menu. Having added a new reference will
force Access to recompile everything.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
"Stephen Raftery" <StephenRaftery@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:499F3010-1381-4875-B1A4-E62FCB2206F8@xxxxxxxxxxxxxxxx
Can anyone please help!
I have been running a database for several years, with several VB
procedures
in a variety of forms.
I have recently started thinking about upsizing to a server based
database,
so I downloaded MSDE200a desktop server emulator to see how it works.
Ever since then, all my VB procedures have gone haywire. i have SQl
statements that refuse to execute, claiming duplicate keys or similar; I
get
data conversion type errors because fields that should be simple integers
now
appear as dates, and string fields that will not accept string input, and
many such things.
I have tried disabling the MSDE and rebooting, but I cannot get rid of it.
More to the point, I cannot see why the presence of MSDE should affect the
running of pure Access files.
I would appreciate any assistance
I am using MS Office Pro 2003 under WXP Pro
Stephen
- Follow-Ups:
- Re: Data corruption with SQL server installed
- From: Sylvain Lafontaine
- Re: Data corruption with SQL server installed
- References:
- Re: Data corruption with SQL server installed
- From: Sylvain Lafontaine
- Re: Data corruption with SQL server installed
- Prev by Date: Re: Question re: 'group by' and 'count' function in Access 2003
- Next by Date: Re: Combination of fields
- Previous by thread: Re: Data corruption with SQL server installed
- Next by thread: Re: Data corruption with SQL server installed
- Index(es):
Relevant Pages
|
Loading