This was also prevalent with CF Updater 7.0.1 and as some
have
found out is also present with the 7.0.2 updater.
At this point in time the only thing I have found to do is
install the
CF Server 7.0.0 version, which does not cause the problem and
do not install the updaters.
I also uninstalled the CF Server completely, downloaded the
most current CF Server version (7.0.2) and tried it as
opposed
to just processing an updater. The same problem is still
present.
The Adobe staff really needs to take a look at this and get a
fix out for it.
Me too. Same problem and same versions as CoffeeCup
Bill
"CoffeeCup" <webforumsuser@macromedia.com> wrote in
message
news:e83s00$jpj$1@forums.macromedia.com...
>I am using Dreamweaver 8.0.2 and ColdFusion 7.0.2
>
> From some our members our user group is seem this
problem is in ColdFusion
> 7.0.1 & 7.0.2. Version 7 doesn't have the same
problem.
>
> I look forward to your guys sorting this out
> Thank you
>
same here...
Just downloaded and installed CF7 today, DW8 with latest
updates.
and, like the others, I would love to see this fixed!
However, I should add... the example db tables seem normal.
( there are 4 databases already in the list in DW )
I only see this problem on my own .mdb file, just added from
within DW.
--
Michael Evangelista
"DataPacks.com" <info@REMOVEdatapacks.com> wrote in
message
news:e85u8v$496$1@forums.macromedia.com...
> Me too. Same problem and same versions as CoffeeCup
>
> Bill
>
>
> "CoffeeCup" <webforumsuser@macromedia.com> wrote
in message
> news:e83s00$jpj$1@forums.macromedia.com...
>>I am using Dreamweaver 8.0.2 and ColdFusion 7.0.2
>>
>> From some our members our user group is seem this
problem is in
>> ColdFusion
>> 7.0.1 & 7.0.2. Version 7 doesn't have the same
problem.
>>
>> I look forward to your guys sorting this out
>> Thank you
>>
>
>
Guys, I do see the same behavior using 7.0.2 and DW MX 2004.
I will submit a bug for this. Not sure how fast this can be fixed
though. I'll try to keep you posted.
It looks like everything works fine if you select Microsoft
Access with Unicode driver instead of just Microsoft Access. So the
problem is wth Microsoft Access driver and this is what I will
submit bug for. Meanwhile, as the workaround, you can change your
datasources to use Access with unicode driver.
Unfortunately, Access Unicode driver has its own problems. So
before changing anything make sure that your application still
works fine. If not, then it might not be a good option for
you.
Aargh. Yet another good argument for mySQL I suppose.
Any idea on a timeline when we might see a DW fix?
--
Michael Evangelista
Evangelista Design / Evangelista Consulting, inc.
www.evangelista-web.com
Custom Small Business Website Solutions
"dimaint" <webforumsuser@macromedia.com> wrote in
message news:e8glr3$8rm$1@forums.macromedia.com...
> It looks like everything works fine if you select
Microsoft Access with Unicode
> driver instead of just Microsoft Access. So the problem
is wth Microsoft Access
> driver and this is what I will submit bug for.
Meanwhile, as the workaround,
> you can change your datasources to use Access with
unicode driver.
>
I have submitted this bug and it was replicated by our OQ
department. So now it is all in hands of development. We will have
a call with them tomorrow to discuss this issue and see when this
can be fixed. I will update you as soon as we know something
new.
Has there been any work done to fix this bug? This is really
bothersome. Using Dreamweaver 8 and Dreamweaver MX2004 with CF
7.0.2 and the problem persists.