Hi,
I tried your suggestions. Although the results where better
than my efforts before - I am able to access all data after
check and synchronize - there is still a big problem:
Every time I try do synchronize the database now, Axapta
wants to remove all new tables (only defined in the
Hi Stefan,
you need to clean up the system table SQLDictionary to avoid loosing data when moving objects to a lower ID.
You need to create a class that scan the data dictionary in Axapta and match that to the SQLDictionary on name not on id as the standard.
You can browse the SQLdictionary
Hi,
I have tried exporting and importing data - importing
into new tables failed, while new fields in existing
tables worked fine.
Stefan Osterburg
Harry Deshpande wrote:
Hi
'in the database. I would like to avoid exporting and
importing with IDs.'
I guess then you will
Be aware, in som tables, like the batch-table, records are save with reference to e.g. classids. When you move your code, classids, tableids and so on changes, and then you loose your reference. No way of export/importing data resolves this issue. We have tried in vain to make MBS support us
Hi,
I have to integrate my axapta with another system. This system is a weighing machine system.
The weigh-bridge calculates the truck's weight continuously. We must get the empty and full weight of the truck by a button click or another way.
Do u know or did u before work in this
Have you copied all aod-files from your standard folder to empty standard\old folder?
Axapta compares the standard with the standard\old folder for upgrade process.
That means in your standard\old folder should exists all aod files from 2.5 sp4 and in you standard folder all 3.0 sp2 files.
Hi erika,
a few month ago, we run into the same situation.
We found out that the setup-program for Ax 3.0/SP2 copies the file axSYS.aod
into the OLD folder of the axapta-application (which shouldn't be done
'cause the axSYS.aod from the Ax 2.5 should be placed there).
The data-upgrade
Hello,
When I run the form tutorial_Thread and click Start, I get this error:
(Thread: 65535) Infolog
Object 'FormRun' could not be created.
But the error only occours in some applications. Why is that?
Regards,
Lars
[Non-text portions of this message have been removed]
The answer to my own question is, that in the info.init... something method, a check on clientType is performed in SP3. If the type is thread, an infolog window is now spawned. The clienttype thread is supported from SP2 and upwards but only implemented in this way in SP3.
Regards,
Lars
hello,
can anyone tell me how to force paper orinetation on a report? i have
made some reports in axapta, and my users dont have the ability to
change the paper orientation.
so i would like to know how to allow my users to do so, and also how
to code into the report the paper orientation.
Hi Wolfgang,
not completely correct.
The setup of the servicepacks ask at a point if you are doing an
upgrade within a 2.5 to 3.0 upgrade or not. Depending on that answer
the files are copied or not.
btw you should also run the pre synchronize data upgrade.
br
Karsten
--- In [EMAIL
Hi,
I want to be able to get the Payment Advice report that is produced for
Cheque AP payments when i make non cheque payments. From what I understand
I must first on the Method of payment (e.g. 'Cash') set a EXPORT File format
and then in the payment journal use the Functions/Generate
Hi Baran,
I think this code helps you.
COM comRows,
comWorkSheet,
comRow;
COMVariant comRowVariant;
int _row;
;
comRows = comWorkSheet.rows();
comRowVariant = comRows.item(_row);
comRow = COM::createFromVariant(comRowVariant);
comRow.delete();
--- In [EMAIL PROTECTED], Baran
13 matches
Mail list logo
