Problem with upsizing to mysql..."Relation corrupt"

[Ted Giles]

Yes, essentially.

[ampapa]

Again, I appreciate the insight.

So, are the Alpha "Indexes" more like macro's associated to buttons that in turn return a resultset in a form/report?

[Ted Giles]

There are no Indexing options shown against an SQL table in the Alpha IDE.

Double click on a SQL table in the Alpha IDE
View the records
Try creating a Query - Server Side
Try the same with Client Side
Note the difference.

Server side is quick, Client side requires all of the data to be downloaded so can be slow.
There is an AUTOMATIC function which decides whether to use Client or Server side based on volume of records - when you create a Query you will see the option of an explanation.
Read this as it describes the Automatic process and you will be familiar with the Query construction which you can then use and it will be held locally and available to use with a Button.

Suggest you convert all of the Indices to Queries and attach them to Buttons.

As for finding which indices are in use, if you don't have A5DOC, then you may need to look at the buttons you mention and change them one at a time.

[ampapa]

Many thanks for the reply Ted.

With my unfamiliarity with the application, is this a form related problem? These don't appear to be actual indexes on the tables...

How do I know what forms are utilizing the "indexes"? ID there somewhere I can see a list of them?

Just trying to figure out what it is I'm trying to solve for here..

VB,

[Ted Giles]

Moving DBF to SQL is only data.
It doesn't recreate forms or indices, that's up to you.
SQL indices are a little special, so beware.
Research Where Clause and Order By.

Suggest you start with a simple form attached to one table, then try filters and selection based on Where etc.

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

... and another road block just appeared, ugh!

So I was successful in linking my table and migrating my data to mysql. However, when opening some of the forms I'm seeing references to missing "Indexes".

SNAG-0479.jpg

and of course all of the indexes are missing... here is a picture of some of them.

SNAG-0480.jpg

The documentation doesn't say anything about deleting the indexes???

Any ideas on how to get around this problem?

Thanks for any ideas or suggestions.

I'm resurrecting this project again to try and help get my friend over the hump with his upsizing project and I was unable to get any resolution to the index problem that appeared after migration. I don't see any direction in the documentation nor can I find any suggestions or hints on the website or via Google search, definitely stuck here!

Can anyone assist with a solution on how to migrate or recreate the missing indexes? From what I can find he has a handful that I will need to be address.

SNAG-0478.jpg
I'm guessing these need to be recreated in SQL, but where and how do I link them back to the forms using them??

Further researching and digging hasn't found a solution to this problem so any help or suggestions would be much appreciated.

Thanks,

VB,

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

Anyone have any thoughts or ideas on how to address forms that have buttons tied to indexes (filters) that no longer work after linking tables to MySQL?

Is it possible to attach straight SQL to them eliminating the indexes?

Thanks,

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

... and another road block just appeared, ugh!

So I was successful in linking my table and migrating my data to mysql. However, when opening some of the forms I'm seeing references to missing "Indexes".

SNAG-0339.jpg

and of course all of the indexes are missing... here is a picture of some of them.

SNAG-0341.jpg

The documentation doesn't say anything about deleting the indexes???

Any ideas on how to get around this problem?

Thanks for any ideas or suggestions.

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

It's in the Help section.Once again, please explain what you are aiming to do.
Is POS point of sale?
Are the two pcs linked in any way?

Yes, POS = Point of Sale... the PC's are networked.

So, I'm finding out the the POS machine stores the actual data and is the Runtime and the other machine is the Developer machine using a shared drive to access the POS machine. That's kind of backwards from how I would have done it but that helped me clear up my confusion, thanks to your information about "Shadowed" and "Runtime".

I think I'm back on schedule... thanks for the nudges.

[Ted Giles]

Re: Problem with upsizing to mysql..."Relation corrupt"

It's in the Help section.Once again, please explain what you are aiming to do.
Is POS point of sale?
Are the two pcs linked in any way?

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

Thanks Ted.

So this is an existing 2 PC installation that is currently running, a "POS" PC and backend PC.

The PC that I tried to perform the "DB Link" process on gave me the error I posted earlier; however that confused me because the entire Alpha5 application and data is installed on that PC.

I'm unfamiliar with the "Shadowed" and "Runtime" installs... you don't happen to have a link do you?

[Ted Giles]

Re: Problem with upsizing to mysql..."Relation corrupt"

Read the details about using Runtime and Shadowed application installs.
In RT you can run the app from a single server or pc, but you can also have the data on the server but the app shell downloaded to the connected pc''s.
If you let us know what you aim to achieve it might help.

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

Appreciate the response Ted.

Trying to figure out how the distributed system works in Alpha..

Does Alpha operate in a Host/Client mode? meaning a limited client install connects to a host machine containing all of the data/application files?

In this environment it looks like the client has all of the files installed but isn't the "Development" machine? just trying to understand what I'm up against.

Thanks,

[Ted Giles]

Re: Problem with upsizing to mysql..."Relation corrupt"

Yes that is correct. Runtime hasn't got the facidity.
You are atempting to use RT in a Development mode.
Try running the second of your two licenses session on the production pc.

[ampapa]

Re: Problem with upsizing to mysql..."Relation corrupt"

Just a quick follow up on the progress I've made.

I believe that I found the linking functionality, I was looking in the wrong place, its a right click on the desktop-> create new I may have over complicated that... .

I've ran into a slight problem and just wanted to confirm my thoughts. When I was testing on a laptop linking a database it ran without issue and I was able to "replace" or save the newly linked database as the same name as the original, that seemed to work fine.

However, when I attempted the same in PROD I ran into the following error:

SNAG-0338.jpg

Have you seen this error before or anyone for that matter??